virtualbox adding items to GRUB boot menu
 

Hi

I've been playing around with virtual box and have added a few components for it via synaptic

I upgraded kernerl to .17 from .16 a few days back, so had to install the .17 compatible components for virtual box again.

It seems those components have been added to my GRUB boot menu, why is this? and more importantly how can i remove them?

I've attached a screenshot below, I'm still a bit of a newbie with Linux so would really appreciate some advice on how I can clean this up. to boot into linux i select .17-generic, so would be nice to just have that and the safe mode?


http://junk.teamstag.co.uk/files/boot_options.JPG


Please advise..


J

You have to edit /boot/grub/menu.lst. Just comment out any line you don't want to appear on your grub screen by placing a # in front of the corresponding line in menu.lst you don't want to appear. You need root privileges to edit menu.lst, so I guess with ubuntu that could be accomplished with:

$ sudo gedit /boot/grub/menu.lst

menu.lst will come up in a text editor, gedit, and can be edited like in any word processor. The above command should open gedit with admin privileges so you should be able to edit menu.lst.

for reference :

I found a good GRUB gui editor in synaptic called KGRUBeditor

I was able to clean up (ie remove) listings in the grub menu that I didn't need, you can also set background images/colors to make it pretty! ;)

Deffo worth the install if you need to play around with GRUB

J

That (of course) only deletes them from the displayed list. They are all still taking up disk space (do a "ls /boot") - a potential problem if you have a separate boot partition.
Go back into Synaptic and search on "image" in the name. Mark all the ones you want to delete for complete removal.

does that mean i can completely remove duplicates?

like kernel .16 (and .17 as .18 is out)

What I don't really understand is, when you upgrade kernel, why can you still boot into the previous one?

Regards

It's not a duplicate - it's superceded.
And the reason is called fallback - what would you do if the new kernel failed to boot ???.