Javier =?iso-8859-15?Q?Fern=E1ndez-Sanguino_Pe=F1a?= <[EMAIL PROTECTED]> writes:
> On Sun, Nov 23, 2003 at 06:19:39PM +0100, Tobias Grimm wrote:
> > Hi!
> >
> > I'm working on a nvram-wakeup package for a Debian based VDR
> > distribution (c't vdr). nvram-wakeup needs a special kernel-image, that
> > forces a shutdown on the next reboot. Normally this image is installed
> > to /boot and a new section has to be added to lilo.conf:
> >
> > image = /boot/bzImage.poweroff
> > label = PowerOff
> >
> > It wouldn't be a problem to modify the lilo.conf in the maintainer
> > script, but I'm not sure if this is the way this should be done.
>
> Yes it is, it's a policy violation.
>
> >
> > What's the best way to add a section to the lilo.conf during package
> > installation (and remove it when uninstalling)?
>
> If the lilo manager does not provide a script to manage lilo.conf, or does
> not provide a way to "hook" things into it (the answer to both question is,
> I believe, that it doesn't), IMHO you can only add a debconf note telling
> the admin what he needs to do in order to enable the package.
One can dpkg-divert lilo with a script that runs the real lilo with an
alternate config file. But thats realy ugly and only works for one
package at a time.
MfG
Goswin
