public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Quirin Gylstorff <Quirin.Gylstorff@siemens.com>
To: isar-users@googlegroups.com, felix.moessbauer@siemens.com
Subject: [PATCH] classes/rootfs: remove content of /dev in postprocessing
Date: Tue, 23 Apr 2024 11:49:01 +0200	[thread overview]
Message-ID: <20240423095152.1433661-1-Quirin.Gylstorff@siemens.com> (raw)

From: Quirin Gylstorff <quirin.gylstorff@siemens.com>

`/dev` is populated by the kernel/initrd during boot up and non
reproducable.

Use a seperate function as /dev must not be mount before the content
is removed.

Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
---
 meta/classes/rootfs.bbclass | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/meta/classes/rootfs.bbclass b/meta/classes/rootfs.bbclass
index 498fbfd6..1d4bea59 100644
--- a/meta/classes/rootfs.bbclass
+++ b/meta/classes/rootfs.bbclass
@@ -340,6 +340,14 @@ python do_rootfs_postprocess() {
 }
 addtask rootfs_postprocess before do_rootfs after do_unpack
 
+# use a seperate function instead of postprocessing as dev should
+# not be mount on removal
+do_rootfs_clean_dev[network] = "${TASK_USE_SUDO}"
+do_rootfs_clean_dev() {
+    sudo rm -rf "${ROOTFSDIR}/dev/"*
+}
+addtask rootfs_clean_dev before do_rootfs after do_rootfs_postprocess
+
 python do_rootfs() {
     """Virtual task"""
     pass
-- 
2.43.0


             reply	other threads:[~2024-04-23  9:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23  9:49 Quirin Gylstorff [this message]
2024-04-23 10:45 ` MOESSBAUER, Felix
2024-04-23 20:39   ` Jan Kiszka
2024-04-24  8:28     ` MOESSBAUER, Felix

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=20240423095152.1433661-1-Quirin.Gylstorff@siemens.com \
    --to=quirin.gylstorff@siemens.com \
    --cc=felix.moessbauer@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