Fast Upgrade to VB 2.0 from the Command Line

[Ron Olsen]

It's now possible to do a direct F14 to F16 upgrade, thanks to a fix from Fedora. I wrote a new wiki page describing how to do this:*How to Upgrade VB 1.10 to VB 2.0: Fast Method

This new procedure avoids the intermediate upgrade to Fedora 15 in the old procedure:*How To Upgrade from VB 1.10 to VB 2.0 Using the Command Line

The new procedure should take about half the time of the old procedure.

I tested the new procedure on a VortexBox 1.10 Virtual Machine running under Parallels on my Mac, and it worked fine. I don't have any real hardware to test on, however, as my VBA has already been upgraded to VB 2.0.

I encourage users to try the new procedure instead of the old one, and report results in this thread.

[paltomare]

Thanks for this Ron.

With your help a while back I made some changes to my VBA to have an Artist/Album/ directory structure. Would this method maintain those changes?

[Ron Olsen]

After the upgrade, you'll have to check /etc/ripit/config to make sure it has your changes to dirtemplate, etc. There may be a /etc/ripit/config.rpmsave file that has your changes.

[divreg]

Hi Ron,

I would just like to confirm again that the new*preupgrade-1.1.10-1.fc14*still doesn't address the issue with /boot being on the RAID array. *Users with RAID systems still cannot upgrade regardless of their fedora system.

[dcm]

Is there no way to do this upgrade without the graphical installer? When I first set up my vortexbox I had a monitor in the house to use - now, its the only non-laptop I own... so I have nothing to display any graphics on.

[rgro]

I think that's the whole point of the command line upgrade process---you don't need a seperate monitor and keyboard in order to do it.*

You can*attempt the upgrade*by logging into your vortexbox via*the terminal emulater on a Mac or via using something like PuTTY or WinSCP on PC's.*

There's plenty of resources here for you to read on this subject, but the basic process is to open your chosen terminal program, login with your VBA's IP address, use password "vortexbox" (unless you set it up as something different) and you'll hopefully*see the command line prompt/cursor.

Then, you start the command line upgrade process by typing in the first command per the instructions.

rgro

[Ron Olsen]

Hi Ron,

I would just like to confirm again that the new*preupgrade-1.1.10-1.fc14*still doesn't address the issue with /boot being on the RAID array. *Users with RAID systems still cannot upgrade regardless of their fedora system.


That's correct. See http://fedoraproject.org/wiki/.....n_F16_bugs

[dcm]

rgro said:


I think that's the whole point of the command line upgrade process—you don't need a seperate monitor and keyboard in order to do it.*


Yeah, I get that and I always do log in to my vb via ssh – however, the instructions this post refers to specifically speaks to a "Graphical Installer" starting up in the last step. I was just wondering if there was any way to not have the graphical installer be used. Most versions of Red Hat/Fedora had an option to install or upgrade via non-graphical CLI – its a shame if that option is no longer available. If it is available, what are the commands or flags to use it instead?

Thanks for responding though!

[Ron Olsen]

The Fedora Graphical Installer displays on a monitor directly attached to the VortexBox.
It does not produce any output to a remote login session (which is disconnected when the Fedora Installer is running).

See http://info.vortexbox.org/tiki.....ge=Upgrade for what to expect when you use a remote login to do the CLI upgrade.

[darrenf]

dcm said:


Is there no way to do this upgrade without the graphical installer? When I first set up my vortexbox I had a monitor in the house to use – now, its the only non-laptop I own… so I have nothing to display any graphics on.


I too don't have a monitor, and always upgrade my May 2009 vintage*vortexbox appliance over ssh. This is a machine which started off with FC10, vortexbox-0.6.2. As of about half hour ago, after upgrading 985 packages, it's running vortexbox-2.0.4 . Predictably I got the warning about a lack of space in /boot which I needed to fix prior to rebooting into the installer; this page helped me figure out how to do it safely (by using yum to remove old kernel packages).