On Tue, 2010-08-24 at 16:55 +0200, Michael Prokop wrote: > * Ben Hutchings <ben@decadent.org.uk> [Tue Aug 24, 2010 at 03:45:36PM +0100]: [...] > > If you insist on installing such a package in the live system then it > > needs to support a safe configuration where it won't do anything until > > the user configures it to. It doesn't matter whether it's invoked by > > the kernel, initramfs-tools, or anything else. It *must* require user > > configuration. > > Jepp. But isn't this (possibility for user configuration) exactly > what Colin is requesting? No, he was asking for a way to disable hook invocation (which is something of a blunt tool). > 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? Report a bug on lilo; I suppose it should warn but still 'succeed' if /etc/lilo.conf is missing. elilo should do the same. This is my bug and I can fix it. :-) No idea about zipl but I doubt you care about s390 live media. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part