Kenneth Schneider wrote: > <snip> > > You might want to re-check this. I just upgraded to the new kernel and > it deleted the old one. The link to the "old kernel" actually points to > the new one. The new one just uses the full name instead of the link. > >
I figured out what happened ... and you are correct. I had installed a copy of .25 from command line earlier so I had 2 kernels when the update came in, .25 and .31. The update erased .25 but left .31 then menu.1st was updated to reflect the contents of /boot correctly. Interesting bug that I will exploit to ensure I always have a backup kernel to go to when updates come in. I'm going to try and repeat the experiment. The trick apparantly is to NOT let Yast do the rpm install of one of the kernel rpms so the erasure doesn't occur, then you have 2 kernels in /boot. Dunno why they don't do it that way by design? Thanks for pointing out the error, indirectly the bug and an idea for a useful exploit that may come in handy next time we get a kernel with an oops built in as an update. Richard -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
