From: Anton Mikanovich <amikan@ilbers.de>
To: Henning Schild <henning.schild@siemens.com>, isar-users@googlegroups.com
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH] image: remove / entry from fstab template
Date: Fri, 14 Oct 2022 15:10:50 +0300 [thread overview]
Message-ID: <14e25495-1b18-b5a0-d088-3367cbf49a2d@ilbers.de> (raw)
In-Reply-To: <20221004114629.27275-1-henning.schild@siemens.com>
04.10.2022 14:46, Henning Schild wrote:
> An fstab entry for / should usually not be required. It just makes a
> rootfs less portable (USB vs. NFS, vs. SSD). The kernel is the one
> that should know which fs to mount and how. That is done via a bootloader.
>
> Should additional mount options be needed for a concrete image, an
> imager like wic might add an entry. i.e. for adding fspassno or
> x-systemd.growfs
>
> So to make the rootfs more generic and to allow imagers to add their
> individual / lines, instead of having to modify an existing one, remove
> the line from the template.
>
> Signed-off-by: Henning Schild <henning.schild@siemens.com>
Applied to next, thanks.
next prev parent reply other threads:[~2022-10-14 12:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 11:46 Henning Schild
2022-10-04 11:53 ` Henning Schild
2022-10-04 11:54 ` Jan Kiszka
2022-10-04 12:21 ` Henning Schild
2022-10-11 18:03 ` Anton Mikanovich
2022-10-13 15:00 ` Henning Schild
2022-10-14 12:08 ` Anton Mikanovich
2022-10-14 16:27 ` Klincov, Wadim
2022-10-14 17:18 ` Anton Mikanovich
2022-10-14 12:10 ` Anton Mikanovich [this message]
2023-01-05 13:08 ` Florian Bezdeka
2023-01-06 4:58 ` Moessbauer, Felix
2023-01-06 8:54 ` Florian Bezdeka
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=14e25495-1b18-b5a0-d088-3367cbf49a2d@ilbers.de \
--to=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@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