Re: [FYI] lilo can not parse compact

[Mark van Walraven <markv@wave.co.nz>]

On Sun, Jan 02, 2000 at 04:00:48PM -0800, Ross Boylan wrote:
> Hmm, I'd think dbootstrap would call liloconfig.  Seems like a potential
> duplication of effort and synchronization problem.

Not really, dbootstrap only has to create /target/etc/lilo.conf and write
a few lines:

	fprintf(filep,"boot=%s\n",boot);
	fprintf(filep,"root=%s\n",Root->name);
	fprintf(filep,"install=/boot/boot.b\nmap=/boot/map\n");
	fprintf(filep,"delay=20\nimage=/vmlinuz\n\tlabel=Linux\n");
	fprintf(filep,"\tread-only\n");

and then run lilo (if required).  Liloconfig is well able to parse a
valid lilo.conf, so there should be no synchronisation problems.

> I believe I did get the message saying to use the rescue disk to boot the
> system.

Thanks.  That matches what I see in the code.

I plan to modify dbootstrap to generate correct boot and root lines for
DAC960 and SMART2 devices, so I'll also take the opportunity to add
some descriptive comments in the generated lilo.conf, whenever there
are problems determining the root or boot parameters.

> You or other suitably empowered person should feel free to reclassify the
> bug to boot-floppy, if appropriate.

I'm not able to do this.  Adam, perhaps?

Regards,

Mark.