Re: [PATCH 1/1] expand-on-first-boot: Use proper first-boot semantics

[Henning Schild <henning.schild@siemens.com>]

If this does not work on buster and maybe ubuntu versions we might
carry, we can not merge this.
We will have to find a way to use the old way for buster and the new
way for versions that actually do work.

Or what does "does not work with buster" actually mean? Will the
overall systemd status turn red and the resize fail, or will it be a
problem we can consider minor?

Henning

Am Wed, 10 Aug 2022 21:26:45 +0200
schrieb Tobias Schmidl <tobiasschmidl@siemens.com>:

> We can now rely on systemd's ConditionFirstBoot to determine whether
> we should run or not.
> 
> Signed-off-by: Tobias Schmidl <tobiasschmidl@siemens.com>
> ---
>  .../expand-on-first-boot/files/expand-on-first-boot.service | 6
> +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git
> a/meta/recipes-support/expand-on-first-boot/files/expand-on-first-boot.service
> b/meta/recipes-support/expand-on-first-boot/files/expand-on-first-boot.service
> index fda5001..7c686c8 100644 ---
> a/meta/recipes-support/expand-on-first-boot/files/expand-on-first-boot.service
> +++
> b/meta/recipes-support/expand-on-first-boot/files/expand-on-first-boot.service
> @@ -8,13 +8,13 @@ Description=Expand last partition
> DefaultDependencies=no Conflicts=shutdown.target
> After=systemd-remount-fs.service -Before=local-fs-pre.target
> shutdown.target -ConditionPathIsReadWrite=/etc
> +Before=local-fs-pre.target shutdown.target
> first-boot-complete.target +Wants=first-boot-complete.target
> +ConditionFirstBoot=true 
>  [Service]
>  Type=oneshot
>  ExecStart=/usr/share/expand-on-first-boot/expand-last-partition.sh
> -ExecStartPost=-/bin/systemctl disable expand-on-first-boot.service
>  
>  [Install]
>  WantedBy=sysinit.target