[Mageia-discuss] Bug or Feature?

Thomas Backlund tmb at mageia.org
Sat Apr 7 20:07:25 CEST 2012


07.04.2012 20:59, imnotpc skrev:
> On 04/07/2012 12:43 PM, Wolfgang Bornath wrote:
>> 2012/4/7 imnotpc<imnotpc at rock3d.net>:
>>> 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
>>
> I don't think it effects this output, but just so you know I deleted 
> most of the unused entries from the grub menu and moved the most recent 
> version to the top so it would boot again if there was a power failure. 
> The curious thing is I expected vmlinuz-3.3.1-desktop-1.mga2 to be here 
> but it isn't. This box has received every update that has come out.
> 
> [root at Cedar1 jalaramie]# ls -l /boot
> total 20792
> -rw-r--r-- 1 root root     440 Apr  7 08:14 boot.backup.sda
> lrwxrwxrwx 1 root root      27 Apr  7 08:17 config -> 
> config-3.3.1-desktop-2.mga2
> -rw-r--r-- 1 root root  135041 Feb 16 09:36 config-3.2.6-desktop-3.mga2
> -rw-r--r-- 1 root root  136931 Apr  4 06:15 config-3.3.1-desktop-2.mga2
> drwxr-xr-x 2 root root    4096 Mar 21 19:03 dracut/
> -rwxr-xr-x 1 root root  537088 Apr  3 14:22 gfxmenu*
> drwxr-xr-x 2 root root    4096 Apr  7 08:14 grub/
> -rw-r--r-- 1 root root 5715971 Apr  3 14:22 initrd-3.2.6-desktop-3.mga2.img
> -rw-r--r-- 1 root root 5733762 Apr  5 07:32 initrd-3.3.1-desktop-2.mga2.img
> lrwxrwxrwx 1 root root      31 Apr  5 07:32 initrd-desktop.img -> 
> initrd-3.3.1-desktop-2.mga2.img

You are missing the symlink initrd.img -> initrd-3.3.1-desktop-2.mga2.img

that is used on default setups...

--
Thomas


More information about the Mageia-discuss mailing list