Re: lilo udebization

[Gergely Risko <risko@atom.hu>]

Hello!

> We definatly need boot loaders (at least one for each arch) to integrate
> into either cdebconf or debconf, but it doesnt need to be a core
> component.
> 
> Core componenents should be just enough to start the install process.
> 
> A boot loader can be fetched by whatever fetch method is supported if it
> isnt on the initial boot medium.

Hmm, now I'm a bit confused.
In cvs/doc/walktrough.txt Joey wrote:
-snip-
It calls another program to parse the file, and get a list of available
modules on the CD. It then asks the retriever to download them each in
turn, and unpacks (but doesn't configure) each of them. A bunch of modules
are unpacked (including a hard drive driver module, a partitioning module, a
disk formatter and mount module, a swap setup module, a base system installer
module, a lilo installer module, and a rescue floppy creator module). Then it
exits.
-snip-

He wrote that lilo installer will be a module. But to lilo-configurator
can set up lilo before the first reboot to work it needs lilo. Or I'm wrong?
This is why I done a lilo.udeb, because it will be downloaded if a retriever
module find it. So why Joey said that we won't need a lilo and a grub udeb?
Joey! If you have got one or two minutes please clear me what do you think
how will the lilo work? You said I need to install boot-loader to the base-
system (before the first restart? with chroot?). 

> Glenn

Gergely