Joachim Schrod wrote:
Your main problem will be that (1) RPMs won't be there any more, (2) RPMs changed their name without any indication what their previous or new name is, and (3) you'll need new RPMs that you even don't know in advance about and that are not listed as dependencies. Alone the name of the kernel packages and associated kernel modules have changed several times between 9.x and 10.3.
Therefore, this upgrade will probably be a manual experience for you...
Joachim
---- I don't have to worry about kernel modules. I generally run my own vanilla kernel downloaded and built for my machine from kernel.org. Am a bit "behind" now...as I'm still running 2.6.24 on most of my machines, but I'll get to 2.6.25 before too long. I'm aware of modules changing names. It's not to difficult to figure out what's what, but I was wondering if anyone had already written a utility or toolset to do what I've been doing manually as I was developing a tool to automate some of the busy work and was trying to gage how many people might find such tools useful -- that is, tools to do manual updating -- "cherry-picking" from new releases, as it were, with the eventual overall movement being toward a complete update. It *always* has been a manual experience for me -- since suse 7.x. Why shouldn't I hope that linux would evolve up to the current level of Win(XP) or even 1990's "Unix" vendors. Requiring the machine be off line for upgrades is anachronistic. Even installing a new kernel would be done on live machines, with a reboot needed to activate the new kernel. But to require the machine be down for hours while someone manually upgrades it? Its just so...primitive. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org