[ATrpms-users] Re: FC2 to FC3 dist-upgrade
Axel Thimm
Axel.Thimm at atrpms.net
Tue Apr 12 13:26:20 CEST 2005
On Tue, Apr 12, 2005 at 08:19:54PM +1000, Phill Edwards wrote:
> > Ok, maybe I was bored, but I decided that it was time to upgrade my FC2 box.
> >
> > I copied sources.list from another FC3 box just recently installed.
> >
> > Then I ran apt-get update && apt-get dist-upgrade:
>
> I've been putting off the FC3 upgrade. I didn't know upgrading to FC3
> was as easy as this. Is this recommended, or would it be better (less
> error prone) to download some FC3 ISOs, burn them to CDs and do a CD
> upgrade?
The safest way is to reinstall, but I have used the apt-get
dist-upgrade to go FC2->FC3 w/o problems, too. If you want to play
safe the release notes to FC3 have some text on how to do a
non-anaconda upgrade. The installation of the mentioned packages can
be made with apt-get. But I think all of these steps are performed by
an apt-get dist-upgrade anyway.
> Systems upgraded to Fedora Core 3 using Anaconda will automatically
> be
> reconfigured to use udev. However (although NOT recommended) it is
> possible to perform a "live" upgrade to udev using the following
> steps:
>
> 1. Ensure that you are running a 2.6 kernel
>
> 2. Ensure that /sys/ is mounted
>
> 3. Install the initscripts RPM supplied with Fedora Core 3
>
> 4. Install the new udev RPM supplied with Fedora Core 3
>
> 5. Execute /sbin/start_udev
>
> 6. Install the new mkinitrd RPM supplied with Fedora Core 3
>
> 7. Perform one of the following steps:
>
> . Install the new kernel RPM supplied with Fedora Core 3
>
> OR:
>
> . Re-run mkinitrd for your existing kernel(s)
>
> Warning
>
> Improperly performing these steps can result in a system
> configuration
> that will not boot properly.
--
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-users/attachments/20050412/9203cfd0/attachment.bin
More information about the atrpms-users
mailing list