"Jacob Westenbach" <westy528@yahoo.com> wrote in message news:<hsgRa.79778$xg5.27257@twister.austin.rr.com> ...
> <rxl124@hehe.com> wrote in message
> news:8a1229a0.0307160936.5f7e6a7a@posting.google.c om...
> > I have redhat 8.0
> >
> > I am experimenting w/ lilo and see if I can make it
> >
> > actually, i am tring to make it that lilo boot up sequence will fail
> >
> > I tried few things
> > 1)messing w/ lilo.conf
> > 2)removing lilo.conf all toghether
> > 3)moving or messing w/ /boot folder
> >
> > NONE of them make it fail to boot up linux.
> >
> > What is going on?
> > Can someone tell me what's going on w/ this ???
>
> I can't imagine why you would want booting to fail, but what you need to do
> is relatively simple.
>
> login
> su -
> cd /etc
> edit lilo.conf to offer no boot options for linux
> save lilo.conf
> run lilo
> exit (back to login)
> logout
> reboot
>
> If you retained any bootable options (e.g. memtest) that will be offered.
> NOTE: you will now need a boot floppy or recovery disk to boot linux.
>
> If what you're wanting is a way to completely keep lilo from running, boot a
> DOS disk and run "fdisk /mbr" to re-write the master boot record of the
> disk. Again, you'll need a boot floppy or recovery disk to boot Linux.
>
> JW

I guess the reason I am doing is I want to learn about the boot
process.

Now, my question is, I went ahead and did mess w/ lilo.conf(even
removed it) and then ran /sbin/lilo -v -v. which would not compile.
Does lilo program look at /etc/lilo.conf when it boots?
Also does lilo program(when in booting process), look at /boot
directory?

I guess above would be more valid question.

Please let me know.

thank you.