On Wed, 2009-01-07 at 08:03 +1100, The Wassermans wrote: > On Fri, 2009-01-02 at 09:21 +1100, Dave Hall wrote: > > > I personally keep the previous kernel for a few days to make sure that > > everything works properly. > > > > > 3. How would I go about deleting them? > > > > Using GNOME go system > admin > synaptic package manager > > > > Search for "linux-image" > > > > Don't try to remove the highest numbered entry (that will be the kernel > > you are running) > > > > For the remaining "linux-image-2.6.xx-y*" entries, just right click on > > them and select "Mark for complete removal". It will ask you to confirm > > that you also want to remove the related restricted modules package as > > well. > > > > When done click Apply. Confirm that you are happy with the changes by > > clicking apply. Wait for synaptic to work its magic. > > I did all of that Dave. Actually, I did the above for Kernel #16, as a > test. Upon re-booting the pesky #16 was still there. So I re-booted and > selected #16 and got the error message: "file not found". I have tried > all the remedies suggested by the other members but nothing seems to get > rid of the long list of Kernels at start-up. > > Not that it's all that important really. It's just a matter of > aesthetics. And the frustration at trying to fix something that should > be quite easy
I know in earlier versions of ubuntu that the menu.lst wasn't always properly updated. try running sudo update-grub from a terminal/the console. Sorry for not replying to your previous post, been distracted by work and the heat :( Cheers Dave -- ubuntu-au mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-au
