Oleg Goldshmidt wrote:

Shachar Shemesh <[EMAIL PROTECTED]> writes:



Oleg Goldshmidt wrote:



Shachar Shemesh <[EMAIL PROTECTED]> writes:



It doesn't have this feature


Are you saying that grub's "fallback" does not work?



Reading the docs, this should not work. "Fallback" is good for a
situation where either the kernel, initrd or root device cannot be
found BY GRUB. In such a case, grub will detect the problem and
fallback to another image. We're talking about a situation where
everything is there, but incorrectly set up. Grub cannot know that
there is a problem under such a situation.

This is from reading the docs. I'm trying this out and will let you
know.



Please do, because I am reading the docs differently:


I'm sorry, I thought my "summary" post would have made it clear what the results were. "fallback" does NOT work as a "lilo -R" replacement.

Now, to tell you the truth I have not had a chance to use this option.
I found out about it only recently, I had thought lilo -R was the
clinching part for using LILO rather than GRUB on kernel development computers. Please post your experiences.


I have one computer (my laptop) where LILO takes close to a minute to load the kernel and initrd from the disk. GRUB does it in an instant. If ever I need a lilo -R replacement on that computer, I'll probably do the double menus trick to get it working. You can as well, if it's really important to you. It shouldn't be too difficult to set up, especially if your compiled kernel always has the same name.

            Shachar

--
Shachar Shemesh
Lingnu Open Source Consulting
http://www.lingnu.com/


================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]



Reply via email to