boot loader

nakkaya · 01-23-2003, 04:15 PM

i have redhat and my lilo.conf and grub.conf are both empty i am trying to change the delay time at start is it possible and by the way can get rid of the boot loader and directly load linux cause its my only os.

bulliver · 01-23-2003, 04:21 PM

If you use grub just change the "timeout" line to 0. I don't know about lilo.

nakkaya · 01-23-2003, 04:38 PM

i know but the problem is file is empty with nothing

deadbug · 01-23-2003, 04:46 PM

One of them has to have something. In Red Hat 8.0, you should find the file /etc/grub.conf or /etc/lilo.conf. If you didn't change to LILO during the install process, you have Grub installed. You have the instructions above for changing grub.conf--it is the same change in lilo.conf if you are using that.

Only root can edit these files, so make sure you are logged on as root. If you can't find them, as root, open a terminal window and type:

whereis grub.conf

bulliver · 01-23-2003, 04:55 PM

Quote:

my lilo.conf and grub.conf are both empty

Jeez, I missed that. You best be making yourself a boot floppy before you reboot then....

I think deadbug is right though, unless you recently (read: since you last booted your system up) deleted the two files manually then your system would not boot, and would essentially be useless. Have another look.

Oh yeah... in RH8 grub.conf is at /boot/grub/grub.conf so I would assume lilo is /boot/lilo/lilo.conf

nakkaya · 01-23-2003, 04:58 PM

yep working thx for the tip

bulliver · 01-23-2003, 04:59 PM

I'm dying of curiousity...how did you fix it?

nakkaya · 01-23-2003, 05:04 PM

whereis grub.conf
then changed the time out to 0

Proud · 01-23-2003, 05:07 PM

So it did have content?

nakkaya · 01-23-2003, 05:12 PM

yes but last time i opened it was empty i am sure some one mentioned logging as root but i always log as root i dont have another acc.

Proud · 01-23-2003, 05:14 PM

WTF? You just said you opened it and altered a setting already in there, but also say it was empty?!

deadbug · 01-23-2003, 05:16 PM

Yes it did; when you "open" a file that should have something in it and it doesn't, the first thing you check is if you pointed at the right directory for the file and aren't merely creating a new one.

In other words, Proud, there are only a few places that you can open grub.conf (/etc/grub/grub.conf and its link file, /etc/grub.conf); everywhere else your text editor will create a new file.

Proud · 01-23-2003, 05:19 PM

Ooh

So can you easily stop it doing that, or is it a matter of command line arguments, or different shell or something?

bulliver · 01-23-2003, 05:31 PM

Quote:

So can you easily stop it doing that

You need to know where your files are

Actually with vim it will say along the lines of:

Code:

grub.conf    (new file)

at the bottom of the screen. I make that mistake quite a bit myself, I just didn't clue in to it here...

Proud · 01-23-2003, 05:34 PM

Ah ok, thanks.