I have a Ubunut 9.10 server that has no grub.conf or /boot/grub/menu.1st file (at least that i can find)? The system boots fine. Is there a different grub configuration file in 9.10 or am i just looking in the wrong place?

Thanks

Grub 2 is now the default boot loader for buntu 9.10. The default file system is ext4. You need Grub 2 to read ext4 file systems. The config file is now called grub.cfg. The default location is /boot/grub/

Here is a link if you want to read more. http://www.linuxtoday.com/news_story...05-35-OS-HL-SW

In Ubuntu 9.10 it's /etc/default/grub

Handy reference to the new grub config file.

OK, thanks, that helps.

I still don't see which file I need to modify to tell the system where the kernel is (e.g. /boot). Reason is that I need to move /boot from it's own seperate partition to under the / partition. Any idea where I do this?

Thanks

The last link leads you here -->https://help.ubuntu.com/community/Gr...0Custom%20Menu

There are examples of how to add a custom menu, including a new kernel. You will have to do a little reading.

Thanks.

However, I still think I am missing something because of the following strange behavior.

The goal of what I am trying to do is to move /boot from it's own partition (/dev/sda1) to the / partition (/dev/sda2). I was able to do this by making a new /boot directory, copy everything from the original /boot, then unmounted /boot and moved the new dir to /boot under /. Modified fstab to remove the reference to original /boot and ran update-grub. upon reboot this worked. Out of curiousity I remounted /dev/sda1 on /mnt and deleted all the old /boot files and dirs that were there, rebooted, but then the system wouldn't boot. I had to go back in with a rescue CD, mount /dev/sda1 and copy all the files and dirs from the new /boot to /dev/sda1, rebooted and it worked. So why does it matter that there be the old /boot stuff on an unmounted file system????? It just doesn't make sense. Does anyone know what's going on here? Clearly I am missing something.

Thanks

I suspect you did not update the correct files for grub2. You do not edit grub.cfg file.

In order to make changes, you edit this file '/etc/grub.d/40_custom' file. Then you run update-grub to modify the grub.cfg file.

Have a close look at the sample updates. Three should be one there that is close to what you need to do. The uuid's will be different. You have to get them from your own system.

Hope this helps.

I did not edit the 40_custom file, but I did run update-grub and I guess it searches the system because it found the new /boot (dev/sda2). When I ran this /dev/sda1 was unmounted. After I ran that I did check grub.cfg and it had the right entries, set root=(hd0,2). But something is still telling it to look at /dev/sda1. If I leave /dev/sda1 alone, unmounted, the system boots and uses the /boot from /dev/sda2. I verified this by cd /boot and doing a df . which shows it is mounted on /dev/sda2. If I delete the files in /dev/sda1 or delete the partition completely it will not boot. Could this have something to do with the MBR?

Where are the sample updates for 40_custom?

How do I determine UUID's?

Thanks again.

I went here-->https://help.ubuntu.com/community/Gr...0Custom%20Menu as posted above and cut and pasted the above from that page. This is just one example, there are more.

Open a konsole, run the command 'sudo blkid' and it will give you some output like this...

This is from my system. They will be different from your system, you should get one for each partition.

The only way you are going to get this to work, as you want is to edit 40_custom file, and then run 'update-grub. The custom entry needs to point to the new /boot directory you are making.