Re: [PATCH 1/1] enable-fsck: don't run update-initramfs after fstab modification

["'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>]

On 21.01.22 08:42, Uladzimir Bely wrote:
> On first machine run, if enable-fsck recipe was enabled, it takes
> much time to start because of spending too much time on
> the 'update-initramfs -u' call.
> 
> Removing it while it really does nothing useful.
> 
> Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
> ---
>  meta/recipes-support/enable-fsck/files/enable-fsck.sh | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/meta/recipes-support/enable-fsck/files/enable-fsck.sh b/meta/recipes-support/enable-fsck/files/enable-fsck.sh
> index d09e35df..72d6bd78 100644
> --- a/meta/recipes-support/enable-fsck/files/enable-fsck.sh
> +++ b/meta/recipes-support/enable-fsck/files/enable-fsck.sh
> @@ -12,5 +12,3 @@ set -e
>  ROOT_DEV="$(/bin/findmnt -n -o SOURCE /)"
>  sed -i -e 's|^/dev/root\([ 	]\+.*[ 	]\+\)0[ 	]\+0|'"$ROOT_DEV"'\10	1|' \
>         -e 's|^\(/dev/.*[ 	]\+\)0[ 	]\+0|\10	2|' /etc/fstab
> -
> -update-initramfs -u

This was wrong, unfortunately: The original purpose of this whole recipe
is to generate an initramfs that contains all tools needed to perform
early filesystem checks. As this information is not available at the
time we build the rootfs, only after wic ran, I once decided achieve the
desired effect by recreating the initramfs on first boot.

If anyone has a better idea how to model that more elegantly, I'm all
ears. Otherwise, we need to revert this and address the boot time issue
by reducing the number of targets where it is run.

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/70095639-d103-4e7f-8c26-1f79b80efe9c%40siemens.com.