Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Tobias Schmidl" <tobiasschmidl@siemens.com>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/1] wic/plugins/images/direct: Allow changes in fstab on rootfs
Date: Thu, 19 May 2022 15:34:01 +0200	[thread overview]
Message-ID: <20220519153401.0d3d92b3@melee> (raw)
In-Reply-To: <20220517184816.1348026-2-tobiasschmidl@siemens.com>

Hello Tobias,

Il giorno Tue, 17 May 2022 20:48:16 +0200
"Tobias Schmidl" <tobiasschmidl@siemens.com> ha scritto:

> Allow wic to also manipulate the rootfs entry in fstab, which it
> currently refuses to write. Reasons one might want to do that include
> using systemd-growfs via --fsoptions on /
> With this change / is now handled exactly the same as other
> mountpoints, the former exception seemingly was not even documented.
> 
> Signed-off-by: Tobias Schmidl <tobiasschmidl@siemens.com>

The autobuilders found some errors while building with this patch on my
testing branch:

https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/3600/steps/15/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/3544/steps/14/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/3566/steps/14/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/3606/steps/14/logs/stdio

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2022-05-19 13:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 18:48 [PATCH 0/1] wic/plugins/images/direct: Allow changes in fstab on rootfs Tobias Schmidl
2022-05-17 18:48 ` [PATCH 1/1] " Tobias Schmidl
2022-05-19 13:34   ` Luca Ceresoli [this message]
2022-05-19 15:07     ` [OE-core] " Schmidl, Tobias

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=20220519153401.0d3d92b3@melee \
    --to=luca.ceresoli@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=tobiasschmidl@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