On Sun, 2006-01-15 at 09:44 -0500, Carl Hartung wrote:
On Sunday 15 January 2006 08:10, Felix Miata wrote:
There's nothing to rollback or reverse when a kernel package is added rather than replaced. My original query is about installing an additional/new package, not a package replacement update/upgrade.
Thanks, Felix, I think we're getting somewhere.
I suspect most people on this list would interpret your original question as I did, along this vein:
A scenario where you've applied a kernel update with YOU that somehow breaks your system... you're seeking a "non rpm command line" solution, i.e. a graphical function in YOU or YaST2 to completely reverse the update including keeping the rpm database in sync.
Now, after much digging, it seems you are actually talking about something related, but completely different:
You want to add and have the option to boot from alternative kernels in such a way that, when booted, the appropriate differences are automatically reflected in the (active?) rpm database.
Having just changed to Suse after using Mandrake/Mandriva since its
beginings I think I can comment on this. Urpmi is configured, by
default, to install and not update kernels. The old kernel is added to
the boot list, giving you the possibility of getting the machine going
if the new kernel gives problems.
That said, in the case of kernel source it just upgrades, you could
therefore be in the situation of kernel and kernel source being out of
sync.
The existance of 2 different kernels gives no problem.
I must say when I first did an update on Suse I was a little scared by
the default action.
--
Dave Cotton