ANNOUNCE: dkms 2.0.17

[Brinkman, Alexander]

> 


 
--------------------------------------------------------
Read the latest update on SAFETUG, a Joint Industry Project on tugs in waves.
This e-mail and its content are subject to the disclaimer and General Conditions at www.marin.nl
-----Original Message-----

> From: dkms-devel-bounces at dell.com [mailto:dkms-devel-bounces at dell.com]
On > Behalf Of Matt Domsch
> Sent: vrijdag 22 juni 2007 7:09
> To: dkms-devel at dell.com
> Subject: ANNOUNCE: dkms 2.0.17
> 
> DKMS 2.0.17 is now available.  Big change is the addition of Ubuntu
> 7.04 Feisty Fawn support, with new actions 'mkdeb' and 'mkdriverdisk
> -d ubuntu'.  Note, 7.04 can't actually load driver disks.  This has
> been fixed in Gutsy.  DKMS also recognizes the install, uninstall, or
> update of the linux-image and linux-headers deb packages, and invokes
> the autoinstaller in these instances, even before reboot.

It would seem that the new Ubuntu stuff that was introduced still has a
little bug in it. Or better said: probably DKMS is ok, but the hook
mechanism is not working correctly anymore.

With DKMS 2.0.17 the file /etc/kernel-img.conf now reads:
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
postinst_hook = /sbin/update-grub
postrm_hook   = /sbin/update-grub
header_postinst_hook = /etc/kernel/postinst.d/dkms

When this last line is in the config file the previous lines are not
called anymore (the postinst and postrm hooks). So update-grub is not
executed anymore on a kernel update (or remove), which is not good.

It can fairly easily be fixed by adding a link in the
/etc/kernel/postinst.d directory to /sbin/update-grub.

But I'm not really sure why the hooks in the config file are not used
anymore. Perhaps because the /etc/kernel/* directories were empty
before, and now there's a dkms script in them (which would maybe
overrule the postinst/postrm_hook entries in the config file?). However,
when removing the last line from the kernel-img.conf file, update-grub
is again called upon installation of a new kernel... very confusing...

Maybe someone who is more into this can explain this behaviour?

Best regards,
  Alexander Brinkman.