Re: [DRAFT] Policy for Linux kernel, initramfs, boot loader update process
- To: debian-kernel@lists.debian.org
- Cc: Stephen Powell <zlinuxman@wowway.com>, Jonas Smedegaard <dr@jones.dk>, William Pitcock <nenolod@dereferenced.org>, Manoj Srivastava <srivasta@debian.org>, debian-devel@lists.debian.org
- Subject: Re: [DRAFT] Policy for Linux kernel, initramfs, boot loader update process
- From: maximilian attems <max@stro.at>
- Date: Mon, 28 Jun 2010 10:45:33 +0200
- Message-id: <[🔎] 20100628084532.GA23241@stro.at>
- Mail-followup-to: debian-kernel@lists.debian.org, Stephen Powell <zlinuxman@wowway.com>, Jonas Smedegaard <dr@jones.dk>, William Pitcock <nenolod@dereferenced.org>, Manoj Srivastava <srivasta@debian.org>, debian-devel@lists.debian.org
- In-reply-to: <[🔎] 1277690555.26161.532.camel@localhost>
- References: <[🔎] 1277690555.26161.532.camel@localhost>
On Mon, 28 Jun 2010, Ben Hutchings wrote:
> 2. Packages for boot loaders that need to be updated whenever the files
> they load are modified must also install hook scripts in
> /etc/mkinitramfs/post-update.d. Initramfs builders must call these
> scripts using run-parts after they create, update or delete an
> initramfs. The arguments given to these hook scripts are the kernel ABI
> version and the absolute path to the initramfs image.
Please rename to more generic /etc/initramfs path.
mkinitramfs is initramfs-tools specific.
otherwise ack.
> 3. Initramfs builders must complete their work before returning from the
> kernel postinst hook script. [initramfs-tools currently uses a trigger
> to defer this because it can also be invoked twice, but this means it
> also has to know how to update specific boot loaders.]
not twice but multiple times, if you upgrade together for example
udev, lvm2, cryptsetup, mdadm and linux-2.6.
> 4. During a kernel package installation, upgrade or removal, various
> boot loader hooks may be invoked (in this order):
>
> a. A postinst_hook or postrm_hook command set by the user or the
> installer in /etc/kernel-img.conf
> b. A hook script in /etc/mkinitramfs/post-update.d
> c. A hook script in /etc/kernel/postinst.d or .../postrm.d
>
> To avoid unnecessary updates, the hooks invoked at step a and b may
> check whether $DPKG_MAINTSCRIPT_PACKAGE begins with 'linux-image-' and
> do nothing in this case. [Is this sensible or is it too 'clever'?]
what is the intent of that point?
sorry you lost me here.
> 5. Kernel and initramfs builder packages must not invoke boot loaders
> except via hooks. If /etc/kernel-img.conf contains an explicit
> 'do_bootloader = yes', kernel package maintainer scripts should warn
> that this is now ignored.
for backward compat and upgrade purpose from lenny,
I think the must is wrong.
> 6. The installer must not define do_bootloader, postinst_hook or
> postrm_hook in /etc/kernel-img.conf.
> ---
thanks
--
maks
Reply to: