On Wed, 2010-06-23 at 23:31 +0200, Jonas Smedegaard wrote:
> On Wed, Jun 23, 2010 at 10:12:42AM -0400, Stephen Powell wrote:
>
> >That does seem like a more general-purpose solution, rather than having
> >lilo and zipl treated as special cases. But please keep the appropriate
> >parties informed of any future design changes to update-initramfs.
> >I myself have never used yaird, but I assume that to be consistent it
> >should have a similar hook system.
>
> A great while back initramfs-tools and kernel packages broke the ABI
> coordinated across initramfs-tools, linux-2.6, yaird and kernel-package.
>
> Sure would be nice with a stable ABI again, and getting informed if it
> changes.
That is a separate issue. What we need here is an interface for the
initramfs builder to update the boot loader if necessary. No such
interface exists yet, AFAIK.
I suggest something like the following:
1. Boot loaders that maintain block lists install a script under
/etc/mkinitramfs/post-update.d which takes two arguments: the kernel ABI
version (uname -r) and the absolute path to an initramfs.
2. Initramfs builders call the scripts in this directory after creating,
updating or deleting an initramfs by running:
run-parts --verbose --exit-on-error --arg=$version --arg=$path /etc/mkinitramfs/post-update.d
or similar.
We could alternately use multiple directories or an argument to
distinguish creation, update and deletion. However, I suspect that
these scripts will need to invoke the same command in all cases.
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