From: Uladzimir Bely <ubely@ilbers.de>
To: Clara Kowalsky <clara.kowalsky@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH v3] expand-on-first-boot: Ensure that /tmp is writable
Date: Wed, 31 Jul 2024 09:46:24 +0300 [thread overview]
Message-ID: <e227148add94c87e5066242bc01b82c18a907a5a.camel@ilbers.de> (raw)
In-Reply-To: <20240725141729.1344298-1-clara.kowalsky@siemens.com>
On Thu, 2024-07-25 at 16:17 +0200, 'Clara Kowalsky' via isar-users
wrote:
> By setting PrivateTmp, a new file system namespace is created for
> this
> service and private /tmp/<service>/tmp and /var/tmp/<service>/tmp
> subdirectories are mounted, which are only used for processes of this
> namespace. The service unit receives a mount unit dependency for all
> mounts required to access /tmp and /var/tmp.
> This ensures that the /tmp directory is writable for the service, as
> mktemp is used in expand-last-partition.sh and creates a temporary
> file.
>
> Signed-off-by: Clara Kowalsky <clara.kowalsky@siemens.com>
> ---
> .../expand-on-first-boot/files/expand-on-first-boot.service | 1
> +
> 1 file changed, 1 insertion(+)
>
> 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..8e76998b 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
> @@ -16,6 +16,7 @@ Type=oneshot
> ExecStart=/usr/share/expand-on-first-boot/expand-last-partition.sh
> ExecStartPost=-/bin/systemctl disable expand-on-first-boot.service
> ExecStopPost=-/bin/systemctl disable expand-on-first-boot.service
> +PrivateTmp=true
>
> [Install]
> WantedBy=sysinit.target
> --
> 2.45.2
>
Applied to next, thanks.
--
Best regards,
Uladzimir.
--
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/e227148add94c87e5066242bc01b82c18a907a5a.camel%40ilbers.de.
next prev parent reply other threads:[~2024-07-31 6:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 14:17 'Clara Kowalsky' via isar-users
2024-07-31 6:46 ` Uladzimir Bely [this message]
2024-08-13 9:17 ` Uladzimir Bely
2024-08-13 9:24 ` 'MOESSBAUER, Felix' via isar-users
2024-08-13 10:32 ` Uladzimir Bely
2024-08-15 4:07 ` Uladzimir Bely
2024-09-03 7:20 ` 'MOESSBAUER, Felix' via isar-users
2024-09-03 9:05 ` 'Jan Kiszka' via isar-users
2024-09-03 18:05 ` 'Florian Bezdeka' via isar-users
2024-09-03 19:49 ` 'Jan Kiszka' via isar-users
-- strict thread matches above, loose matches on Subject: below --
2024-07-24 13:39 'Clara Kowalsky' via isar-users
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=e227148add94c87e5066242bc01b82c18a907a5a.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=clara.kowalsky@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