argh, grub woes

[Ted Ozolins]

Net Llama! wrote:

> On 11/25/2004 11:36 AM, Bruce Marshall wrote:
>
>> On Thursday 25 November 2004 02:18 pm, Collins Richey wrote:
>>
>>> On Thu, 25 Nov 2004 14:13:30 -0500, Bruce Marshall <bmarsh at bmarsh.com> 
>>
>
>>> I disagree. grub.conf and/or menu.lst in the older grub must be
>>> available at boot time to build the menu list of bootable systems.
>>> That's why you don't have to run grub after modifying the conf as is
>>> the case with lilo. At install time, grub stores its own pointer to
>>> the "root" you have specified so that it can find the conf when you
>>> boot.
>>
>>
>>
>> And I'll raise your disagree.....    I have always had a 
>> /etc/grub.conf  (even in the last Caldera release I think) and it was 
>> all about install and nothing about actually booting.  On SuSE it is 
>> still in /etc/grub/conf and does not need to be present for boot.
>>
>> If you are saying that if I rename it, I can't boot, I'll bet a 
>> 6-pack of your favorite beer on it....
>>
>> Yes, there does need to be a menu.lst.
>
>
> On Fedora, menu.lst and grub.conf are the same thing.
>
>
Perhaps on RH or SuSe, but I have not used menu.lst since Caldera days. 
I have both Gentoo and Slackware on various systems here and none of 
them use menu.lst, not even a symlink. I have grub.conf in /boot/grub 
and nowhere else. I've gone through numerous kernel upgrades and 
rebooted many times without a glitch.


-- 
Ted Ozolins(VE7TVO)
Westbank, B. C