Michael Mansour wrote:
>>How did you do it via ATrpms?
> 
> 
> ATrpms mirror the SL directories, so I upgraded to the yum 2.4.0 of ATrpms,
> installed the atrpms and medley-package-config rpm packages, did a "yum
> check-update", and then "yum -y update rpm1 rpm2 rpm3 ..." of each of the
> packages showing up as "sl-release".
> 
> I made note to not install the yum-conf from SL (which conflicted with the
> medley-package-config from ATrpms) and the rpmdb-SL from SL (which broke yum),
> everything else was sweet.
> 
> Axel has also just added the upgrade path for SL41 to SL42, which this shows
> when run from SL41:
> 
> sl-release: ################################################## 1543/1543
> Added 1543 new packages, deleted 0 old in 21.93 seconds
> 
> SysVinit.i386                            2.85-34.3              sl-release
> alsa-utils.i386                          1.0.6-4                sl-release
> apr.i386                                 0.9.4-24.5             sl-release
> apr-util.i386                            0.9.4-21               sl-release
> apt-sourceslist.i386                     42-1.SL                sl-release
> at.i386                                  3.1.8-78_EL4           sl-release
> etc...


It is fine with me, but why should one do all these, instead of just upgrading to 
ftp://ftp.scientificlinux.org/linux/scientific/42/i386/SL/RPMS/yum-conf-42-3.SL.noarch.rpm 
and just do a "yum upgrade", by following the standard SL point release, upgrade procedure?