[olug] upgrade from Fedora 17 to Fedora 18

[Lou Duchez]

That sounds easier than what I did, and I bet it's more approved than 
using yum.

The one thing I can say for yum is, it can be done remotely, over SSH.  
It sounds like fedup can't.  But if you have direct physical access to 
the computer, looks like fedup is the way to go.

> Since preupgrade has gone away, I used it's replacement, the oddly 
> named 'fedup'.  I upgraded my laptop and my workstation with it.  It 
> worked alright.  If you haven't read the release notes, you probably 
> wouldn't know about it.  The Fedora 18 DVD download cannot upgrade 
> previous releases.  I don't know if that will be the norm going 
> forward, or a result of the development window in re-writing the 
> installer, which was one of the factors for the delay of F18.  There 
> may be more info in blog posts or videos resulting from this past 
> weekend's FUDcon in Lawrence, Kansas.
>
> You can only upgrade 17 to 18.  So, if you are on anything older, 
> you'll need to get to 17 first.  If that is the case, it's easier to 
> do a fresh install of 18.  I did a fresh install of 18 on my home 
> desktop mainly because I was going from i386 to x86_64.
>
>
> First, make sure you have Fedora 17 updated to the latest packages.
>
> Next, install fedup in Fedora 17 -
> sudo yum install fedup
>
> Perform the package download -
> sudo fedup-cli --network 18 --debuglog fedoradebug.log --instrepo 
> http://mirror.chpc.utah.edu/pub/fedora/linux/releases/18/Fedora/x86_64/os/ 
>
>
> The --instrepo switch is optional, as fedup will search for a mirror 
> to use.  I used it to choose a faster mirror to download the upgraded 
> packages.
>
> Once the downloads are done, fedup will modify grub2 to put an upgrade 
> entry in it's boot menu.
>
> Now reboot.  The upgrade option should be first. Select and wait.
>
> Some observations:
> The install screen shows a progress bar.  You can press Escape to see 
> individual package process.
> The screen does blank during the upgrade, but don't panic.  It's safe 
> to press Shift to wake up the screen to see what's going on.
>
> Jon L.
>
> On 01/20/2013 02:45 PM, Sam Flint wrote:
>> If only i had that yesterday! had to do a reinstall...
>>
>>
>> On Sun, Jan 20, 2013 at 7:39 AM, Lou Duchez <lou at paprikash.com> wrote:
>>
>>> So last time a new Fedora came out (Fedora 17), I posted my upgrade
>>> instructions, which were kind of hairy.  That's because it was a Very
>>> Special Upgrade, where they were merging the /bin, /sbin, and /lib
>>> directories with /usr/bin, /usr/sbin, and /usr/lib respectively.  So it
>>> required a fair amount of hand-holding.
>>>
>>> But lest you get the wrong idea about Fedora, the upgrade from 
>>> Fedora 17
>>> to 18 is pretty standard, and here's what it consists of:
>>>
>>> 1) yum update
>>>
>>>      A preventative measure, because it's best to make sure your system
>>> isn't all outdated and weird.
>>>
>>> 2) yum clean all
>>>
>>>      Another preventative measure, to make sure yum isn't all full 
>>> of cruft.
>>>
>>> 3) rpm --import 
>>> https://fedoraproject.org/**static/DE7F38BD.txt<https://fedoraproject.org/static/DE7F38BD.txt>
>>>
>>>      You need a new key to process the new RPMs.
>>>
>>> 4) yum --releasever=18 --disableplugin=presto distro-sync
>>>
>>>      This is what does the updating.
>>>
>>> 5) rpm --rebuilddb
>>>
>>>      This is the only "special" step this time around. There's a 
>>> change to
>>> the yum database structure, so you have to rebuild the yum database 
>>> after
>>> upgrading your system.
>>>
>>> 6) yum repolist
>>>
>>>      This step is just to confirm that you're on the Fedora 18 
>>> repositories
>>> now.
>>>
>>> 7) df -h | grep /boot
>>>
>>>      This is just to determine whether your boot device is /dev/sda,
>>> /dev/sdb, or what.  You'll need that for ...
>>>
>>> 8) /sbin/grub2-install /dev/[device]
>>>
>>>      This installs the new boot loader.  What you need to specify 
>>> here is
>>> the device (/sda), not the partition (/sda1).
>>>
>>> 9) reboot
>>>
>>>      Say a small prayer and reboot.  It'll almost certainly reboot just
>>> fine; I did six servers yesterday and they all came back up.
>>>
>>>
>>>
>>> ______________________________**_________________
>>> OLUG mailing list
>>> OLUG at olug.org
>>> https://lists.olug.org/**mailman/listinfo/olug<https://lists.olug.org/mailman/listinfo/olug> 
>>>
>>>
>>
>>
>
> _______________________________________________
> OLUG mailing list
> OLUG at olug.org
> https://lists.olug.org/mailman/listinfo/olug