On Tue, 2010-08-24 at 16:55 +0100, Colin Watson wrote: > On Tue, Aug 24, 2010 at 04:08:47PM +0100, Ben Hutchings wrote: > > 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). > > Actually, what I want is a consistent way to disable bootloader > invocation for all bootloaders, without necessarily requiring the > bootloader package not to be installed (since that's sometimes extremely > awkward to arrange). Exactly where this goes I can't say I mind. If > the result is an extension to the bootloader/kernel policy that needs to > be implemented in each bootloader package, that would be fine too. [...] OK, so something like this: "Boot loader packages must be installable on the filesystem in a disabled state where they will not write to the boot sector or other non-filesystem storage. While a boot loader is disabled, any kernel and initramfs hooks it includes must do nothing except (optionally) printing a warning that the boot loader is disabled, and must exit successfully." 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