The Ubuntu community has contributed 12357 ideas, 58479 comments, 1187050 votes
Idea
#11139: Delete Old Kernel Entries Feature in Update Manager for Grub (menu.lst)
|
| |
73
|
|
|
Written by JupiterV2 the 15 Jul 08 at 03:19.
Category: System.
Related to:
Update manager.
Status: New
|
|
|
Description
There should be an easier method of deleting old kernels and their grub menu entries. Currently, the update script adds all kernel images in /boot into menu.lst no matter how old. Some administration app or a feature in Update Manager should allow one to delete old kernel images and their menu entries (if the images are removed prior to the script running then its an easy fix). All but the current kernel should be removed, allowing for a stable kernel entry and the new kernel (in case there is some kind of conflict with the newly installed kernel).
The only way to do so currently is the manually delete the kernel image and related file, then edit the grub menu list to delete the old entries.
Attachments
No attachments.
Duplicates
Comments
|
kaens wrote on the 15 Jul 08 at 04:26
| |
I agree. Unless there's a good rationale for it, it seems like the older kernel images and their menu entries should be removed (minus the last stable one, of course)
|
|
Ssdg wrote on the 15 Jul 08 at 05:35
| |
The last stable one might not be the one you work with. Why? because if you use some "home compiled" modules for a webcam or some virtualisation machine (vmware to name it) you might prefer to run it on an old kernel, when you have time to do so, you can recompile it for the new one, but you can't be sure that just 1 kernel had been released while you were using your old modules.
|
|
amlucent23 wrote on the 15 Jul 08 at 07:42
| |
sudo apt-get install startup-manager
|
|
aelfwyne wrote on the 15 Jul 08 at 07:58
|
Was going to point out what amlucent23 just did.
Install startup-manager - it lets you configure exactly how many kernel images remain in Grub.
|
|
Auzy wrote on the 15 Jul 08 at 09:04
|
I actually have another vision in mind.
The problem at the moment is that despite plug and play being possible for devices for longer then a decade now, Linux hard-disk's still aren't, because the only way to boot them is to mess around with Grub.
Grub2 on the other hand will be support scripting, so we could make it automatically detect the entries (so uninstalling a kernel would automatically delete the entry in grub without needing anything to edit grub.lst.
That means they could sell harddisks with linux preinstalled, you just drop them in, and the computer will work fine.
And the only reason people would then edit grub.lst is if they want the detection process to be manual.
So vote for completing Grub2. This would bring us FAR ahead of the current OSX bootloader
|
|
andruk wrote on the 15 Jul 08 at 20:59
|
The featureset of Grub2 sounds incredible, and would most likely solve just about every single problem with GRUB ever.
Unfortunately, it is only slowly updated, and it doesn't look like Grub2 is slated for feature freeze (sort of) until November 2008.
Vote for Auzy's idea if you want this.
Sounds like startup-manager already handles everything in this idea though, so
+0
|
Post your comment
|
|
|
