where is /boot/grub/menu.lst in Ubuntu 9.10 ?

Asked by george_rutkay

What happened in 9.10? I can no longer find the /boot/grub/menu.lst file to edit?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu grub2 Edit question
Assignee:
No assignee Edit question
Solved by:
george_rutkay
Solved:
Last query:
Last reply:
Revision history for this message
Sam_ (and-sam) said :
#1
Revision history for this message
Alexandru Cucu (alexandru.cucu) said :
#2

With the new version of GRUB included in Ubuntu 9.10 you will have to edit: /boot/grub/grub.cfg
If you only want to add custom entries I recommend you to use: /etc/grub.d/40_custom

Revision history for this message
george_rutkay (yaktur) said :
#3

Thanks!

Revision history for this message
george_rutkay (yaktur) said :
#4

Hmm, well this is very strange stuff, I'm sure I don't understand why they changed grub?

I tried the /etc/grub.d/40_custom and this was my response:

root@Dell1:/home/geo# /etc/grub.d/40_custom
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
root@Dell1:

There's nothing to edit! What the heck? What a screwy thing!

I tried to edit the /boot/grub/grub.cfg file (in spite of the warning to not edit it, contained within that same file). I tried to remark out the unwanted portions with # (stuff that pertains to kernels no longer on this system due to incoming updates, old kernels, etc...cleaned up with "Computer Janitor").

Of course I saved the original as a backup file in case something messed up (as it usually does since software often tells lies to people, saying one thing but doing another).

When I restarted, I got a bunch of fast flashing error messages, then it finally booted. So I restored the original file. I don't like seeing error messages, that's not a normal thing!

So I'm quite sure whoever decided, when they were building this 9.10, to switch from normal grub to this funky grub2 stuff, well they must have been smoking crack or something because this switch has just made editing the configuration a whole lot more difficult. They should just make small gradual improvements and not change everything around so you can't make sense of it.

Revision history for this message
Sam_ (and-sam) said :
#5

Disagree in total.
Grub_2 finally takes in account the modular concept of system architectures, hence is highly configurable and one menu.lst alone couldn't handle such advanced tasks.
Nothing screwy or strange here, only strict logical, hence easy to follow or to play with, depending on (subjective) view of user experience.
What's wrong with reading the Wiki and release notes?
What's wrong with learning from errors?

However, no such thing which can't be improved, rational substantial ideas are welcome.
https://wiki.ubuntu.com/KernelTeam/Grub2Testing

btw. it isn't expected that an average user deals with essential config files such as grub.cfg, the goal is 'no need for it'.
The login as root@Dell1 implies at least an advanced user which knows exactly what he/she is doing.
https://help.ubuntu.com/community/RootSudo#root%20account

> nothing to edit!
Of course nothing to edit, it says:
> Simply type the menu entries you want to add after this comment <
Hence, first you need to add something before it can be edited.
Examples:
https://wiki.ubuntu.com/Grub2#Adding%20Entries%20to%20Grub%202
http://members.iinet.net/~herman546/p20/GRUB2%20Configuration%20File%20Commands.html#Custom_Boot_Entries

If you'd define your goal in the first place, lets say removing old kernel images, simple answer would be, search for the images and remove it via Synaptic or CLI.
Removing only entries in config files wont delete images.
Same with Synaptic, Computer Janitor or CLI, what actually appears in GUI and
on CLI (with 'apt-get autoremove') are header files, not the images itself.
The goal is, not to get in trouble by not having a bootable image left.

Synaptic has a sidemenu with a tab called 'status' incl. (local or can be removed)
in there you'll find e.g.
linux-headers-2.6.31-14-generic

A search for linux-image will find e.g.
linux-image-2.6.31-14-generic

Remove by right click on the line -> remove completely, then apply.
Grub will be updated automatically, the process can be viewed in the popup window -> details.
http://www.debianadmin.com/simple-package-management-with-synaptic-package-manager-in-ubuntu.html

Search for images via CLI:
dpkg -l linux-image* | grep ii
Output example:
linux-image-2.6.31-14-generic

Removal cmd e.g.:
apt-get purge linux-image-2.6.31-14-generic
Manually update Grub:
update-grub
https://answers.launchpad.net/ubuntu/+source/update-manager/+question/93412

Enjoy Ubuntu.
https://help.ubuntu.com/community/Signpost

Revision history for this message
george_rutkay (yaktur) said :
#6

In English??

I don't do computers for a living, I build and design RF hardware (transmitters, receivers), I don't do programming. I'm just a computer user who gets stuck fixing computers for family members.

Revision history for this message
Sam_ (and-sam) said :
#7

Me too:
I don't do computers for a living
I don't do programming
I'm just a computer user who, when gets stuck, collects information on how to fix, later on is very happy to understand more about the system, having solved the issue with community help and finally giving back, since I'm using free software and nobody forced me to do so.

Revision history for this message
marossity (marossity) said :
#8

Hi Sam,
That is a good response. It is difficult to understand people. It's free, it's solid, there is tremendous support, and the guys and gals doing the programming are constantly making it better. So "george_rutkay" go cry somewhere else, please.

Revision history for this message
george_rutkay (yaktur) said :
#9

Go to hell. So-called improvements that make troubleshooting harder are of no use!

Revision history for this message
marossity (marossity) said :
#10

"Go to hell" ? Hmmm, I could respond with a sharp answer, like, "Oh yeah!". But I won't. Instead I will just say this.
I googled the new GRUB2 and picked up a tremendous response. I then ran through a couple of the tutorials to LEARN something. I understand GRUB2 and I see it is going to be the next loader. Troubleshooting with GRUB2 is a snap.