On Wed, May 7, 2008 at 11:13 AM, Sam Clemens <clemens.sam1@gmail.com> wrote:
Sylvester Lykkehus wrote:
Out of curiosity from reading this thread.
I have a couple of machines running, which were originally a 10.0 install.
I have done 'live' upgrades of those systems, 10.0 -> 10.2 -> 10.3, and plan on going -> 11.0.
I haven't run into any of the problems described in this thread, or perhaps I missed a point ?
All of those versions use glibc6, so there's no mid-upgrade replacement of glibc5.
I've used the smart package manager for all the upgrades, and my procedure
have been as follows:
Remove all repos Add repo's for new version Do a smart upgrade --update Remove all packages on the system, which is not in the new repo's (get rid
of those packages that was available for e.g. 10.2, but not 10.3)
Both machines function fine, and are not a mess. So, have I been lucky, or
would this be a safe procedure ?
You didn't have to replace glibc, so it's rather trivial.
But I did a 9.3 to 10.1 in-place upgrade (which I thought included the glibc upgrade) using Yast Upgrade (essentially the same process Sylvester mentioned using on-line repositories) and it worked fine. There was one reboot, and it worked fine. -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org