Re: /etc/grub.d/10_linux anomaly
On Tue, Nov 30, 2010 at 4:45 AM, Volkan YAZICI <yazicivo@ttmail.com> wrote:
> On Tue, 30 Nov 2010, Tom H <tomh0665@gmail.com> writes:
>>
>> So 10_linux isn't the problem. Another script is somehow picking up
>> 2.6.32...
>
> It depends. If 10_linux is expected to find currently running kernel as
> well, your are right; otherwise, wrong. I thought that the current
> kernel is somehow automatically added to the list without an
> intervention from /etc/grub.d scripts. Anyway, there still is a problem.
I may have misunderstood your first email, but it seemed to me that
you moved 10_linux out of "/etc/grub.d" and update-grub still added
the kernel in "/boot" to "/boot/grub/grub.cfg".
If you look at grub.cfg, you'll see which script added 2.6.32 because
each of the scripts adds a its own header and footer to its section.
Reply to: