From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: isar-users <isar-users@googlegroups.com>,
Uladzimir Bely <ubely@ilbers.de>,
"Kowalsky, Clara (T CED SES-DE)" <clara.kowalsky@siemens.com>
Subject: [PATCH] expand-on-first-boot: Fix broken syntax
Date: Sat, 31 Aug 2024 10:52:11 +0200 [thread overview]
Message-ID: <3d319203-f9ea-4193-8454-db580cfd7680@siemens.com> (raw)
From: Jan Kiszka <jan.kiszka@siemens.com>
There must be only one path per ConditionPathIsReadWrite statement, or
the two of them will be interpreted as one, and the condition is never
met.
Fixes: 6e2974df ("expand-on-first-boot: Add /tmp to ConditionPathIsReadWrite")
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
.../expand-on-first-boot/files/expand-on-first-boot.service | 3 ++-
1 file changed, 2 insertions(+), 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 9daae719..58f4b55b 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,8 @@ DefaultDependencies=no
Conflicts=shutdown.target
After=systemd-remount-fs.service
Before=local-fs-pre.target shutdown.target
-ConditionPathIsReadWrite=/etc /tmp
+ConditionPathIsReadWrite=/etc
+ConditionPathIsReadWrite=/tmp
[Service]
Type=oneshot
--
2.43.0
--
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/3d319203-f9ea-4193-8454-db580cfd7680%40siemens.com.
next reply other threads:[~2024-08-31 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-31 8:52 'Jan Kiszka' via isar-users [this message]
2024-09-04 8:23 ` Uladzimir Bely
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=3d319203-f9ea-4193-8454-db580cfd7680@siemens.com \
--to=isar-users@googlegroups.com \
--cc=clara.kowalsky@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=ubely@ilbers.de \
/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