On Saturday 06 January 2001 23:04, Lars Wirzenius wrote:
> Russell Coker <firstname.lastname@example.org>:
> > I am working on the Debian package of lilo and am writing code for
> > auto-generating lilo.conf files.
> Presumably, if there is a /etc/lilo.conf file already on the system, you
> will ask whether to keep that as it is or whether to create a new one?
> (I'd like confirmation about this, in light of the other lilo related
The latest package is supposed to ask you whether you want to generate a new
lilo.conf or keep the manually created one (default keep the manual one). If
you select to keep the manual one and you have no lilo.conf file then it'll
create one anyway, but after that it won't touch it.
If you run "liloconfig -f" then you can create a new lilo.conf even though
you've setup debconf to not overwrite old files. Liloconfig also takes a
parameter for an alternate name for lilo.conf (so you can create
/tmp/lilo.conf to see what it would do).
I have had a report that my new package does not behave properly WRT the
"Manually edit lilo.conf" option. I have been unable to reproduce this on
the 6 machines (with different configurations) that I have access to. I am
still looking into this.
The latest package is on http://www.coker.com.au/lilo/ . If you can help me
track down this last problem then I would really appreciate it!
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/projects.html Projects I am working on
http://www.coker.com.au/~russell/ My home page