argh, grub woes

[Collins Richey]

On Fri, 26 Nov 2004 10:46:40 -0500, Bruce Marshall <bmarsh at bmarsh.com> wrote:
> On Thursday 25 November 2004 08:45 pm, Alma J Wetzker wrote:
> 
> 
> > On my gentoo system, there is no menu.lst.  AFAIK, /boot/grub/grub.conf is
> > the only file required anymore.  That file is read at boot.  grub.conf
> > contains the menu, and boot parameters for each menu choice, it can be
> > changed manually during the boot process.  If it is not there, you boot to
> > a grub prompt and have to enter all the boot parameters by hand to get a
> > working system.
> >
> > (menu.lst == grub.conf) is true
> >
> > Some distro's attempt to put all the configuration files in the /etc
> > directory (a sane desire).  The file still needs to be in the /grub
> > directory of the boot partition in order to get a booting system.
> 
> On SuSE 9.2 (the latest)  the grub.conf file is in /etc    and the menu.lst is
> in  /boot/grub.   No symlinks for either.   And the grub.conf file contains
> only install information.   This is the only way I have ever seen grub setup,
> starting with its first use by Caldera.
> 
> Obviously each distro can set it up as they please.....
> 

True. Just keep in mind the following:

1. The /etc/grub.conf file is just a convenient place to store install
info and is totally distinct from what is normally referred to as
grub.conf (the list of menu entries). This file is not really required
by grub, and any name could be used, unless you want to use the
install (rather than setup) method to create the mbr.

2. Yes, grub will work just fine with /boot/grub/menu.lst, but
/boot/grub/grub.conf (not the file SUSE calls /etc/grub.conf! ) is
also valid and used by many distros.

-- 
 Collins