Kam Leo: >> Just save your data and start a new install. It will be much faster. >> After the initial installation there are still the 3rd party >> repository packages to install. What joy! Frank Cox: > I considered that. The only third-party repository that I have actively > installed is Livna, but I have a number of cron jobs and several bits of > custom-compiled (non-rpm) software that I also run on this computer, plus it > is a LTSP server. (I have a nifty little Neoware terminal behind the counter in > my theatre lobby that I use to read books and whatnot while the show is on.) > > As this is my main computer where all of my stuff lives, setting the whole thing > up again from scratch would probably take the better part of a day and a fair > bit of thought, not to mention that there is always one little thing that I > manage to forget about until something suddenly doesn't happen the way that it > should. In the dim and distant past, I'd tried upgrades, and spent ages ironing out the bugs. Later, I did fresh installs, and spent a much lesser amount of time customising the new install. Apart from the time, this seemed to be the differences: One is just re-configuring, the other is sorting out all the problems that aren't handled by the update process. I would think that it'd be good to, prior to an update, scan a system and look for system configuration files that aren't the same as provided by the RPM when installed, back them up, and then use them as templates for re-configuring a new system. -- [tim@bigblack ~]$ uname -ipr 2.6.23.1-10.fc7 i686 i386 Using FC 4, 5, 6 & 7, plus CentOS 5. Today, it's FC7. Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
