2012/4/7 imnotpc <[email protected]>: > On 04/07/2012 09:35 AM, Frank Griffin wrote: >> >> On 04/07/2012 08:51 AM, imnotpc wrote: >>> >>> I just discovered that when a new kernel package is installed the grub >>> menu entry is added to the bottom rather than the top. The result is that >>> the original kernel remains the default and new kernels not used. Most of my >>> systems are only accessed through ssh so I had no idea the new kernels >>> weren't being used and this only came to my attention today when another >>> update, probably dbus, broke the old kernel and hung all my boxes during >>> reboot. >>> >>> I would think that if you install an update the expectation is that it >>> would be used by default. I haven't had time to check yet, but this may also >>> be the cause of other bugs I've been having. Is this a bug or intended >>> behavior? >>> >> Not so. The default uses the symlinks for vmlinuz and initrd which are >> version-independent, and the kernel install redefines them to point to the >> new kernel. The entry tacked on to the end uses the new versoins by name, >> and is there so that after the next new kernel comes along you'll have an >> entry to boot this one if you need to. > > > So the first and last menu entry are the same most recent version? Then this > is probably a bug since the symlink entry won't boot but the entry at the > bottom that lists the version by name boots fine.
Then something went wrong during installation of the new kernel. Could you please show the output of $ ls -l /boot -- wobo
