Re: LILO

[Manoj Srivastava <srivasta@debian.org>]

>>"Brian" == Brian May <bam@debian.org> writes:

 Brian> the boot loader package should be responsible for reinstalling itself,
 Brian> not the kernel image.

	Nobody is reinstalling the boot loader. I would agree that a
 postinst should not trigger the installation of another package.

 Brian> eg: just because I have a copy of lilo installed (maybe I don't
 Brian> entirely trust grub yet), doesn't mean I want lilo to replace my
 Brian> working configuration of grub when I install a kernel-image!

	A simple config file change is all you need to do
 that. However, my reading of the mail I have received to date is that
 the common case, as communicated to me, is that people want not to be
 bothered to do this manually, thus the default. 

	However, kernel-image packages are flexible enough to allow
 you not to have them run lilo, or manage the symlinks, or any of the
 other processing, as you wish. 

 Brian> If, however, it was done by the boot loader, it would be possible to
 Brian> customise it in order to disable it from running lilo.

	Uhh? LILO is a boot loader. So you are going to run lilo and
 customize it not to run itself? Since you can already customize a
 config file not to have lilo ruin, what exactly is the advantage
 again? 

	manoj
-- 
 All of the true things I am about to tell you are shameless lies. The
 Book of Bokonon / Kurt Vonnegut Jr.
Manoj Srivastava   <srivasta@debian.org>  <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C