From: "'Kowalsky, Clara' via isar-users" <isar-users@googlegroups.com>
To: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "quirin.gylstorff@siemens.com" <quirin.gylstorff@siemens.com>
Subject: RE: [PATCH] expand-on-first-boot: Add /tmp to ConditionPathIsReadWrite
Date: Wed, 24 Jul 2024 13:48:08 +0000 [thread overview]
Message-ID: <AS5PR10MB8173EAD442FF61AB5BD496FF93AA2@AS5PR10MB8173.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <ea98d68c3c00f1fb58cc6c09eb23c52f878d089c.camel@siemens.com>
> -----Original Message-----
> From: Moessbauer, Felix (T CED OES-DE) <felix.moessbauer@siemens.com>
> Sent: Thursday, July 18, 2024 9:27 AM
> To: isar-users@googlegroups.com; Kowalsky, Clara (T CED OES-DE)
> <clara.kowalsky@siemens.com>
> Cc: Gylstorff, Quirin (T CED OES-DE) <quirin.gylstorff@siemens.com>
> Subject: Re: [PATCH] expand-on-first-boot: Add /tmp to
> ConditionPathIsReadWrite
>
> On Fri, 2024-07-12 at 16:03 +0200, 'Clara Kowalsky' via isar-users
> wrote:
> > This verifies that /tmp is readable and writable before starting the
> > service.
> >
> > Signed-off-by: Clara Kowalsky <clara.kowalsky@siemens.com>
> > ---
> > .../expand-on-first-boot/files/expand-on-first-boot.service | 2
> > +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > 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 90c92a39..9daae719 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
> > @@ -9,7 +9,7 @@ DefaultDependencies=no
> > Conflicts=shutdown.target
> > After=systemd-remount-fs.service
> > Before=local-fs-pre.target shutdown.target
> > -ConditionPathIsReadWrite=/etc
> > +ConditionPathIsReadWrite=/etc /tmp
>
> Hi, can't we simply use PrivateTmp=true ? This would unshare /tmp and /var/tmp
> from the host / calling environment.
Thanks for the comment. I tested it with PrivateTmp=true and this also works fine.
>
> I'm anyways wondering how the system will behave if /tmp is not writable, as
> having this writable is mandated by systemd.
>
> What data is stored there? If this is potentially big, we should not use /tmp at all
> but instead /var/tmp.
Mktemp just creates an empty directory that is used as mount point, so no need to switch to /var/tmp.
Clara
> Felix
>
> >
> > [Service]
> > Type=oneshot
> > --
> > 2.45.2
> >
>
> --
> 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/AS5PR10MB8173EAD442FF61AB5BD496FF93AA2%40AS5PR10MB8173.EURPRD10.PROD.OUTLOOK.COM.
prev parent reply other threads:[~2024-07-24 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 14:03 'Clara Kowalsky' via isar-users
2024-07-12 14:09 ` 'Jan Kiszka' via isar-users
2024-07-18 7:27 ` 'MOESSBAUER, Felix' via isar-users
2024-07-24 13:48 ` 'Kowalsky, Clara' via isar-users [this message]
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=AS5PR10MB8173EAD442FF61AB5BD496FF93AA2@AS5PR10MB8173.EURPRD10.PROD.OUTLOOK.COM \
--to=isar-users@googlegroups.com \
--cc=clara.kowalsky@siemens.com \
--cc=felix.moessbauer@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