> No no , grub.conf is read on the fly on bootup. You're talking about menu.lst, and you'd be editing menu.lst to change kernel boot options or boot targets.
How does grub find out which partition to find menu.lst on? True, you don't need a grub.conf, you can enter the data manually into grub-install if you feel so inclined. Do a test Nick: copy your /boot onto /, then do a cat /dev/zero >/dev/hda1 (the 32M hdaX which used to contain /boot) and see if it still boots... Actually not a conclusive test, grub might have a fallback and keeps looking on other filesystems until it finds a /boot/menu.lst. What if you have multiple partitions/filesystems all containing a valid (but different) /boot/menu.lst? > > [1] The list of actual disk blocks taken up by the kernel image file is > > hardcoded (ok around 2 corners) into the boot loader. > > not in grub it isn't. You are thinking of lilo. Correct, the [1] was in the lilo part of the sentence... Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
