FC4t2 no good without LILO

[Guy Fraser]

On Wed, 2005-13-04 at 01:00 -0400, Peter Jones wrote:
> On Tue, 2005-04-12 at 23:51 -0400, Matthew Miller wrote:
> > On Tue, Apr 12, 2005 at 05:23:48PM -0700, Mike Bird wrote:
> > > So we have a package that is essential in some circumstances, that costs
> > > next to nothing to maintain, and that takes up <0.1% of a CD's space. 
> > 
> > You're missing a huge part of the picture. Having lilo the package (even
> > though as you note, it's not really maintained) might not be much, but it
> > requires a lot of complicated kludgy infrastructure in the installer, and in
> > mkinitrd, etc., and makes kernel updates very fragile.
> > 
> > *That's* what makes the developers want to drop it -- it's not just to make
> > your life hard.
> 
> And even if all that is present, the model behind lilo is unreliable,
> and has always caused major problems.  When we shipped lilo by default,
> the various incarnations of "LI", "L 01 01 01...", etc were a *major*
> support issue, because reinstalling the first stage bootloader is very
> failure prone.
> 
> -- 
>         Peter


And "ERROR 15" means :

----Start Sample----
Errors reported by the Stage 2
The general way that the Stage 2 handles errors is to abort the
operation in question, print an error string, then (if possible) either
continue based on the fact that an error occurred or wait for the user
to deal with the error. 

The following is a comprehensive list of error messages for the Stage 2
(error numbers for the Stage 1.5 are listed before the colon in each
description): 


1 : Filename must be either an absolute filename or blocklist 
        This error is returned if a file name is requested which doesn't
        fit the syntax/rules listed in the Filesystem. 
2 : Bad file or directory type 
        This error is returned if a file requested is not a regular
        file, but something like a symbolic link, directory, or FIFO. 
...
14 : Filesystem compatibility error, cannot read whole file 
        Some of the filesystem reading code in GRUB has limits on the
        length of the files it can read. This error is returned when the
        user runs into such a limit. 
15 : File not found 
        This error is returned if the specified file name cannot be
        found, but everything else (like the disk/partition info) is
        OK. 
16 : Inconsistent filesystem structure 
        This error is returned by the filesystem code to denote an
        internal error caused by the sanity checks of the filesystem
        structure on disk not matching what it expects. This is usually
        caused by a corrupt filesystem or bugs in the code handling it
        in GRUB. 
...
----End Sample----

One significant problem, there is never a filename listed. :-(

Please see my post with LILO error messages.