On Wed, 13 Sep 2006 15:18:27 +0200, Michael Biebl <[EMAIL PROTECTED]> said:
> And setting
> postinst_hook = /usr/sbin/update-grub
> postrm_hook = /usr/sbin/update-grub
> finally fixes the problem, although the absolute path is not
> recommended by the grub maintainer.
The grub maintainer has not thought through all use cases,
including yours -- changing /etc/kernel-img.conf to not contain
absolute path names while there are kernel images on disk with the
older postrm scripts will cause problems when those packages are
removed.
Since there is no expectation that the location of update-grub
is going to change in the near-to-mid term, there is no harm in using
absolute path lengths right ow -- until your system cycles through
all the older kernel images. Post-etch one can recommend putting in
non-absolute path names in the configuration file, when there are few
installations with kernels that would break. There is no hurry.
> Still, postrm should work if postrm_hook does not specify an
> absolute path (seems to work for postinst after all, which is a bit
> weird).
If you find me a time machine to retroactively fix the
kernel-package used to generate your old kernel image, sure.
Any kernel images created with the current kernel-packagew
will have a working postrm -- but that does not help with the postrem
scripts already sitting in your /var/lib/dpkg/info/ directory.
manoj
--
You scratch my tape, and I'll scratch yours.
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.datasync.com/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
