remove scripts mention lilo

[Peter Berry]

Binary package hint: linux-source-2.6.20

I can still reproduce bug 99511 in this kernel, namely: Ubuntu uses grub, but the remove scripts for the kernel packages mention lilo:

-----
Removing linux-image-2.6.20-16-generic ...
Running postrm hook script /sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.22-14-generic
Found kernel: /boot/memtest86+.bin
Updating /boot/grub/menu.lst ... done

The link /vmlinuz.old is a damaged link
Removing symbolic link vmlinuz.old
Unless you used the optional flag in lilo,
 you may need to re-run your boot loader[lilo]
The link /initrd.img.old is a damaged link
Removing symbolic link initrd.img.old
Unless you used the optional flag in lilo,
 you may need to re-run your boot loader[lilo]
-----

It's not very useful to be told to run lilo when you're not using it! The situation seems to have improved slightly since 2.6.17 in that it refers to "your boot loader", but it still seems to assume lilo. (It's natural to read "your boot loader[lilo]" as "your boot loader, i.e. lilo", which is wrong.)

[Peter Berry (pwberry)]

I'm not willing to try to remove my running kernel, so I don't know if the bug is present in 2.6.22, but I thought it might be worth an "also affects" there to get some attention. :)

[Leann Ogasawara (leannogasawara)]

Hi Peter,

I'm retargetting this report to the upcoming hardy kernel release, hence the 'hardy-kernel-candidate' tag. As I had mentioned in my comment for bug 99511:

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/99511/comments/1

This doesn't really meet the criteria for a stable release so is being marked as 'Won't Fix'. Thanks!

[Peter Berry (pwberry)]

So the 'won't fix' only applies to these versions, and the bug will be refiled against Hardy's kernel later?

It would be nice if the Launchpad pages for kernels give a hint to this policy, as I didn't know it existed (seems sensible though).

[Leann Ogasawara (leannogasawara)]

On Mon, 2007-11-05 at 18:12 +0000, Peter Berry wrote:
> So the 'won't fix' only applies to these versions, and the bug will be
> refiled against Hardy's kernel later?

Correct.

> It would be nice if the Launchpad pages for kernels give a hint to this
> policy, as I didn't know it existed (seems sensible though).

The following "Tags" section of the Kernel Team Bug Policies wiki talks
a little about the 'hardy-kernel-candidate' tag:

https://wiki.ubuntu.com/KernelTeamBugPolicies#head-4bcdb6b3a4f949cd8d9d28adee37e0fcd215cb50

This link does as well:

https://wiki.ubuntu.com/Bugs/Tags

Thanks!

[Leann Ogasawara (leannogasawara)]

Hi Peter,

Hardy Heron Alpha2 was recently released. I just played with removing linux-image-2.6.24-1-generic that I had installed on my system. I didn't see any of the lilo messages you saw:

Removing linux-image-2.6.24-1-generic ...
Examining /etc/kernel/prerm.d.
run-parts: executing /etc/kernel/prerm.d/dkms
Running postrm hook script /sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /vmlinuz-2.6.24-2-generic
Found kernel: /vmlinuz-2.6.24-rc5-custom
Found kernel: /vmlinuz-2.6.22-14-generic
Found kernel: /vmlinuz-2.6.20-16-generic
Found kernel: /memtest86+.bin
Updating /boot/grub/menu.lst ... done

If you ever get to a point where you'd feel comfortable to remove one of your kernels, let us know if this bug still exists for you. For now I'm going to mark it as fixed, but again, please feel free to reopen if you notice it hasn't been resolved. Thanks.