From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: alexander.heinisch@siemens.com, isar-users@googlegroups.com
Cc: quirin.gylstorff@siemens.com
Subject: Re: [PATCH] meta: Add option to specify additional dependencies for package expand-on-first-boot in case an encrypted disk has to be resized
Date: Thu, 5 Sep 2024 06:51:53 +0200 [thread overview]
Message-ID: <3e2f8af4-8ed0-4d21-ad36-891e0b12aea4@siemens.com> (raw)
In-Reply-To: <20240904171614.138923-1-alexander.heinisch@siemens.com>
On 04.09.24 19:16, alexander.heinisch@siemens.com wrote:
> From: Alexander Heinisch <alexander.heinisch@siemens.com>
>
> Although, disk encryption itself is not handled in isar (as of now), downstream projects
> using disk encryption break this package. To mitigate this, we added an additional variable
> to specify debian packages to be installed, when disk encryption is used. Depending on the
> specific implementation (tpm, password prompt, ...) downstream projects can set the dependencies
> needed for their strategy to handle the resize.
>
> Note: We decided against fixing this by bbappending in downstream packages, because we believe
> this approach scales better and is also easier to maintain.
>
> Signed-off-by: Alexander Heinisch <alexander.heinisch@siemens.com>
> ---
> .../expand-on-first-boot/expand-on-first-boot_1.5.bb | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-support/expand-on-first-boot/expand-on-first-boot_1.5.bb b/meta/recipes-support/expand-on-first-boot/expand-on-first-boot_1.5.bb
> index 1b5b066b..ea52ae9e 100644
> --- a/meta/recipes-support/expand-on-first-boot/expand-on-first-boot_1.5.bb
> +++ b/meta/recipes-support/expand-on-first-boot/expand-on-first-boot_1.5.bb
> @@ -10,7 +10,9 @@ inherit dpkg-raw
> DESCRIPTION = "This service grows the last partition to the full medium during first boot"
> MAINTAINER = "isar-users <isar-users@googlegroups.com>"
>
> -DEBIAN_DEPENDS = "systemd, sed, grep, coreutils, mount, e2fsprogs, fdisk (>=2.29.2-3) | util-linux (<2.29.2-3), util-linux"
> +# Additional packages that are needed to resize the disk if it is encrypted.
> +ADDITIONAL_DISK_ENCRYPTION_PACKAGES ?= ""
> +DEBIAN_DEPENDS = "systemd, sed, grep, coreutils, mount, e2fsprogs, fdisk (>=2.29.2-3) | util-linux (<2.29.2-3), util-linux, ${ADDITIONAL_DISK_ENCRYPTION_PACKAGES}"
Maybe time to start wrapping this long line around (I explained around
how ;)).
Jan
>
> SRC_URI = " \
> file://expand-on-first-boot.service \
--
Siemens AG, Technology
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 on the web visit https://groups.google.com/d/msgid/isar-users/3e2f8af4-8ed0-4d21-ad36-891e0b12aea4%40siemens.com.
next prev parent reply other threads:[~2024-09-05 4:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 17:16 alexander.heinisch via isar-users
2024-09-05 4:51 ` 'Jan Kiszka' via isar-users [this message]
2024-09-05 7:21 alexander.heinisch via isar-users
2024-09-05 7:22 ` 'Jan Kiszka' via isar-users
2024-09-09 14:38 ` Uladzimir Bely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3e2f8af4-8ed0-4d21-ad36-891e0b12aea4@siemens.com \
--to=isar-users@googlegroups.com \
--cc=alexander.heinisch@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=quirin.gylstorff@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox