Re: Re: Re: DSDT in initrd

On Thu, 22 May 2003 23:31, Ducrot Bruno wrote:

quoted

On a lot of non x86 platforms Lilo is considerably more featureful.
Initrd basically exists as a way to take an arbitary bootloader and feed
it stuff. In some cases the tools even nail the initrd onto the end of
the binary because the boot loader isnt smart enough to load.

I don't understand.  On a lot of non x86 lilo do not even exist (PPC <-
quick or yaboot, SPARC <- silo) etc.

To be more precise, LILO only exists on i386.  Large amounts of LILO code are 
x86 assembler.  Most of the code in the main /usr/bin/lilo program is 
designed to guess what the BIOS expects and put things in the right place 
(determining IBM PC BIOS codes from Linux device nodes, etc).

Of course you could probably port LILO to a non-x86 platform, but then it 
probably wouldn't be recognisable.  Half the options in /etc/lilo.conf would 
need to be changed or removed.

I'm not sure what Alan means.  But on x86 LILO has many desirable features 
that other boot loaders lack.  LILO supports serial consoles, graphical 
splash screens, and isn't really painful to install.

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page



-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge