* Stephen Powell <zlinux...@wowway.com> [Tue Aug 24, 2010 at 11:18:39AM -0400]: > 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 I'm aware of this, though I'd prefer a clean interface and not hacks. :) Especially since I'm not aware of a way how to chmod -x the files before installing the packages that fail during installation then. ;) regards, -mika-
signature.asc
Description: Digital signature
