From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>,
Christian Storm <christian.storm@siemens.com>
Subject: Re: [PATCH] expand-on-first-boot: Add support for devicemapper
Date: Thu, 21 Apr 2022 20:49:25 +0200 [thread overview]
Message-ID: <8f91bdba-4a0e-3f74-16c4-76acdee238d6@siemens.com> (raw)
In-Reply-To: <20220421194347.21b0b742@md1za8fc.ad001.siemens.net>
On 21.04.22 19:43, Henning Schild wrote:
> I learned yesterday about systemd-repart
> https://www.freedesktop.org/software/systemd/man/systemd-repart.service.html
>
> We should look at this and how mkosi puts/uses it for debian.
>
+ systemd-growfs, yes, these are possibly alternative building blocks
for such a service. Quickly scanned mkosi but couldn't find the require
glue yet, unfortunately.
> Not a review, just a generic remark that there might be more powerful
> and ready to use tools out there. At some point i will play with this
> and see if it can replace expand-on-first-boot, i bet we will soon hear
> the first btrfs stories ... and maybe luks.
>
> I know people do that with isar and their own funny scripting which can
> not be found upstream.
We would surely want to switch here, but we need the right pattern
first. A script or a cascade of dependent and accordingly configured
services will remain, though.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2022-04-21 18:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 17:10 Jan Kiszka
2022-04-21 17:43 ` Henning Schild
2022-04-21 18:49 ` Jan Kiszka [this message]
2022-04-21 19:05 ` Henning Schild
2022-04-22 6:28 ` Tobias Schaffner
2022-04-22 7:21 ` Henning Schild
2022-04-22 9:08 ` Jan Kiszka
2022-05-14 14:05 ` Anton Mikanovich
2022-05-19 11:51 ` Moessbauer, Felix
2022-05-19 12:23 ` Henning Schild
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=8f91bdba-4a0e-3f74-16c4-76acdee238d6@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=christian.storm@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.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