Anaconda upgrade stuff (was Re: Path for upgrading...)

Barry K. Nathan barryn at
Thu Jan 1 12:46:58 UTC 2004

On Thu, Jan 01, 2004 at 12:41:34AM -1000, Warren Togami wrote:
> Anaconda upgrade I'm guessing will be supported from both RH9 and FC1 to 
> FC2.  You may be able to do it using apt or yum too, but I'm guessing 
> that wont properly setup all of the new 2.6 kernel + selinux default 
> policies.
> Anything else apt/yum upgrade to FC2 wont do that Anaconda would?

(Now that I've finished writing this message, I realize that most of
this probably doesn't affect a yum/apt/up2date upgrade from RH9 or FC1,
or from RH 8.0 for that matter. It's important stuff to pay attention to
when upgrading from RH 7.3 or earlier, however, particularly the stuff
that anaconda pulls in when it sees gnome-core.)

Let's see... (Some of these may be handled automatically by yum or apt,
or up2date for that matter if you use it rather than yum or apt, but I'll
mention them anyway.)

If you have any linuxconf packages installed, it removes those.
(Specifically, it removes linuxconf, linuxconf-devel, and

If you have XFree86 on the system, it makes sure to install xterm (since
xterm was split into a package of its own at some point).

If up2date-gnome is installed, it installs rhn-applet as well. (According
to a comment in "if they have up2date-gnome, they probably
want the applet now too since it works in both gnome and kde")

If gnome-core is installed, anaconda makes sure that these other
packages also get installed (this is needed for a complete GNOME 1.x to
GNOME 2.x upgrade):

(This last one is *definitely* not done automatically by up2date. I
don't know about yum or apt.)

Oh, yeah, anaconda also warns you if you're upgrading from anything
earlier than Red Hat 6.2, or if you're upgrading from a system that has
Helix/Ximian GNOME installed.

This is all the stuff that popped out at me when I looked at the
(rawhide) anaconda source code. (I think anaconda from FC 1 was no
different in this regard, though.) There could be other stuff that I
missed, nonetheless...

-Barry K. Nathan <barryn at>

More information about the devel mailing list