Hi Troy,

[..snip..]
> > But what if you want the bugfixes?
> > There are currently 2 things to do, and we're working on a third, 
> > possibly fourth way.
> > 1. Just get it by hand.  Ugg ... that's tedious.
> > 2. Upgrade to the latest release, or possibly even the rolling release. 
> >   Also tedious, but at least you get them all.
> > 3. We're working on a 'bugfix' repository.  It's currently in 4.1.  So 
> > that if you do happen to want a bugfix, you can enable that yum 
> > repository and get it.
> > 4. We're also working on an easy way for users to set things up so that 
> > they will always be updated to the latest release when it comes out. 
> > This is how CentOS does it.  This will not be the default setting.

Option 4 is already available via ATrpms. I was pleasantly surprised when I
upgraded yum to the latest supplied by ATrpms and installed their
"medley-package-config" RPM (via yum). I then did a "yum check-update" and saw
a bunch of "sl-updates" were shown, I selected them all on a "yum -y update"
and about 30mins later my SL40 servers were now SL41.

I've done this on 4 SL40 servers and it worked fine on all without any dramas. 

The /etc/yum.repos.d/base.repo file (installed from medley-package-config)
contains the following:

# cat base.repo
#
#
[release]
name=Red Hat Enterprise Linux 4 - i386 - Base
baseurl=http://dl.atrpms.net/el4-i386/redhat/release
failovermethod=priority
enabled=0

#
#
[updates]
name=Red Hat Enterprise Linux 4 - i386 - Released Updates
baseurl=http://dl.atrpms.net/el4-i386/redhat/updates
failovermethod=priority
enabled=0

#
#
[sl-release]
name=Red Hat Enterprise Linux 4 - i386 - Base
baseurl=http://dl.atrpms.net/sl4-i386/scientificlinux/release
failovermethod=priority

#
#
[sl-updates]
name=Red Hat Enterprise Linux 4 - i386 - Released Updates
baseurl=http://dl.atrpms.net/sl4-i386/scientificlinux/updates
failovermethod=priority

So.. all the works already been done by the ATrpms team to perform these
rolling upgrades.

Michael.

PS. I also did this on my SL303 server to update it to an SL305 server, again
without any dramas, it just works.