-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-01-15 at 09:44 -0500, Carl Hartung wrote:
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.
That Yast does readily: it will replace the existing rpm by the one you force, even if older.
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.
I understood he asked about what what Anders wrote a moment ago, in his first paragraph, using rpm -i instead of -U. There is nothing to reflect in the rpm database at boot time: simply, the database knows there are two kernel versions installed. No problemo :-) - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDymf+tTMYHG2NR9URAsK+AJ9oLj0QlL+CZnFdTSjPpqthZY028gCgh58j 3nfcHvBKsCgu4RZb6NyrNh0= =1EgH -----END PGP SIGNATURE-----