On Tue, 24 Aug 2010 10:55:43 -0400 (EDT), Michael Prokop <m...@debian.org> wrote: > Jepp. But isn't this (possibility for user configuration) exactly > what Colin is requesting? > > I'm for example shipping lilo and grub with the live system (so the > binaries as well as its documentation is available to the user), but > nowadays the build process fails due to errors like: > > run-parts: /etc/initramfs/post-update.d//lilo exited with return code 1 > [...] > run-parts: /etc/kernel/postinst.d/zz-lilo exited with return code 1 > > So the IMHO open question is what's a proper way to disable such > stuff on request?
I am not a member of the kernel team. I'm just an ordinary user. So I speak with zero authority. And Ben may have his own ideas that he wishes to share. But one way to prevent a hook script from executing is to remove its executable attribute. For example, chmod -x /etc/kernel/postinst.d/zz-lilo chmod -x /etc/kernel/postrm.d/zz-lilo chmod -x /etc/initramfs/post-update.d/lilo This is not supported, of course, nor is it recommended. But it will work. As a general rule I agree with Ben. If you don't want the hook scripts to run, don't install the package. But in special situations, such as where you want the man page installed for reference purposes but don't want the package to be used, this is one "solution". I have used this technique to run my own hook scripts instead of the package hook scripts without changing the package hook scripts when the package hook scripts are buggy or incomplete. (But of course I open a bug report against the package too.) -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
