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: the appropriate
info node says "any errors":
- Command: fallback num
Go into unattended boot mode: if the default boot entry has any
errors, instead of waiting for the user to do anything,
immediately start over using the NUM entry (same numbering as the
`default' command (*note default::)). This obviously won't help if
the machine was rebooted by a kernel that GRUB loaded.
and the Configuration node has a sample config file with the following
comment (note the "any reason" wording):
# Fallback to the second entry.
fallback 1
If, for any reason, the default entry doesn't work, fall back to the
second one (this is rarely used, for obvious reasons).
[OG: the "obvious reasons" are not so obvious to me, but that'\s a
different matter].
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.
Thanks,
--
Oleg Goldshmidt | [EMAIL PROTECTED]
=================================================================
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]
