Re: [RFC 1/1] delay creation of initrd until end of rootfs install

["MOESSBAUER, Felix" <felix.moessbauer@siemens.com>]

On Wed, 2024-03-27 at 08:46 +0300, Uladzimir Bely wrote:
> > > > > 
> > > > > Yes, definitely. I reported this on the debian-kernel ML as
> > > > > well:
> > > > > https://lists.debian.org/debian-kernel/2023/12/msg00097.html
> > > > > 
> > > > > Anyways, are there more objections against this patch?
> > > > 
> > > > Any news on this? This is on the ML for quite some time without
> > > > objections. If required, I can send a rebased version.
> > > > 
> > > 
> > > I assume this is held back now by the current -rc cycle. Likely
> > > an
> > > improvement after 0.10.
> > > 
> > > Jan
> > > 
> > 
> > As 0.10 was released,  can we merge this?
> > 
> > Quirin
> 
> Hello all.
> 
> I run it in CI and delaying initrd creation seems to cause errors for
> some targets:
> 
> build/tmp/work/debian-bullseye-armhf/isar-image-base-imx6-
> sabrelite/1.0-r0/temp/log.do_image_fit:
> 
> ```
> FATAL ERROR: Couldn't open "/home/builder/isar-image-base-imx6-
> sabrelite/deploy/isar-image-base-debian-bullseye-imx6-sabrelite-
> initrd.img": No such file or directory
> /usr/bin/mkimage: Can't open /home/builder/isar-image-base-imx6-
> sabrelite/deploy/isar-image-base-debian-bullseye-imx6-
> sabrelite.fit.tmp: No such file or directory
> ```

Hi, I was able to pin-point the issue and I'm working on a workaround /
solution. The problem is, that the symlink initrd.img ->
boot/initrd.img-<version> is not created when installing the kernel, as
we disable the initrd generation completely.

The way how the kernel is installed in Debian is REALLY cumbersome...

Felix

> 
> There were more patchsets applied for this run, but I think that
> others
> are not related.
> 

-- 
Siemens AG, Technology
Linux Expert Center