Kernel changes for initramfs generation

Colin Watson cjwatson at
Tue Nov 29 10:48:22 GMT 2005

On Mon, Nov 28, 2005 at 09:02:18PM -0800, Ben Collins wrote:
> Quick summary, all packages that modify things in the initramfs should
> start using the update-initramfs program.
> For further explanation and details, please see:
> This is part of a dapper spec. The only thing that I know that should be
> using this is usplash, but I can't see why things like busybox-initramfs
> postinst shouldn't be calling it aswell.

I think using it in busybox-initramfs would require a slight amendment
to the spec to avoid a circular dependency: it should probably omit the
dependency on initramfs-tools and instead call 'update-initramfs -u'
only if update-initramfs is available.

That said, what will happen if initramfs-tools and its other
dependencies are unpacked but not configured? This is quite likely on
initial installation or on upgrades from earlier versions of the
distribution. Will update-initramfs bomb out (this would be OK) or would
it generate an incorrect initramfs (this would be rather less good)?

Also, what is the correct error handling behaviour for postinst scripts
calling update-initramfs? Should errors from update-initramfs cause the
postinst to abort, or should they be ignored? The above question is
relevant here too, since packages that are dependencies of
initramfs-tools may not be able to generate a correct initramfs yet.


Colin Watson                                       [cjwatson at]

More information about the ubuntu-devel mailing list