On Tue, Nov 30, 2010 at 4:45 AM, Volkan YAZICI wrote:
> On Tue, 30 Nov 2010, Tom H 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
On Tue, Nov 30, 2010 at 4:45 AM, Volkan YAZICI wrote:
> On Tue, 30 Nov 2010, Tom H 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
On Ma, 30 nov 10, 11:45:05, Volkan YAZICI wrote:
> On Tue, 30 Nov 2010, Tom H 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 thoug
On Tue, 30 Nov 2010, Tom H 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
On Tue, Nov 30, 2010 at 4:25 AM, Volkan YAZICI wrote:
>
> TL;DR --- /etc/grub.d/10_linux causes update-grub to match same Linux
> image twice. (Debian GNU/Linux Squeeze, up-to-date as of date.)
>
> # ls -1F /boot
> config-2.6.32-5-686
> grub/
> initrd.img-2.6.32-5-686
> System.map-2.6.32-5-68
Hi,
TL;DR --- /etc/grub.d/10_linux causes update-grub to match same Linux
image twice. (Debian GNU/Linux Squeeze, up-to-date as of date.)
# ls -1F /boot
config-2.6.32-5-686
grub/
initrd.img-2.6.32-5-686
System.map-2.6.32-5-686
vmlinuz-2.6.32-5-686
# dpkg -l | grep linux-image
i
6 matches
Mail list logo