From: Christian Storm <christian.storm@siemens.com>
To: isar-users@googlegroups.com
Subject: download_dev-random hook question
Date: Mon, 13 Nov 2017 17:35:46 +0100 [thread overview]
Message-ID: <20171113163546.6vcu7fuigxprpwik@MD1KR9XC.ww002.siemens.net> (raw)
Hi,
I just stumbled over the download_dev-random multistrap hook:
Why is it that you only create /dev/{,u}random?
Why not also create other essential files like /dev/{null,zero}
as well, e.g., like this:
```
--- a/meta/recipes-devtools/buildchroot/files/download_dev-random
+++ b/meta/recipes-devtools/buildchroot/files/download_dev-random
@@ -4,10 +4,14 @@ set -e
readonly ROOTFS="$1"
-mknod "${ROOTFS}/dev/random" c 1 8
-chmod 640 "${ROOTFS}/dev/random"
+mknod -m 640 "${ROOTFS}/dev/random" c 1 8
chown 0:0 "${ROOTFS}/dev/random"
-mknod "${ROOTFS}/dev/urandom" c 1 9
-chmod 640 "${ROOTFS}/dev/urandom"
+mknod -m 640 "${ROOTFS}/dev/urandom" c 1 9
chown 0:0 "${ROOTFS}/dev/urandom"
+
+mknod -m 666 "${ROOTFS}/dev/null" c 1 3
+chown 0:0 "${ROOTFS}/dev/null"
+
+mknod -m 666 "${ROOTFS}/dev/zero" c 1 5
+chown 0:0 "${ROOTFS}/dev/zero"
```
Besten Gru�,
Christian
--
Dr. Christian Storm
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Otto-Hahn-Ring 6, 81739 M�nchen, Germany
next reply other threads:[~2017-11-13 16:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 16:35 Christian Storm [this message]
2017-11-13 18:09 ` Henning Schild
2017-11-14 9:06 ` [ext] Christian Storm
2017-11-16 9:04 ` [ext] Christian Storm
2017-11-16 9:19 ` Alexander Smirnov
2017-11-16 9:41 ` Christian Storm
2017-11-16 9:49 ` Alexander Smirnov
2017-11-16 10:04 ` Christian Storm
2017-11-20 9:41 ` Henning Schild
2017-11-20 10:00 ` Christian Storm
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=20171113163546.6vcu7fuigxprpwik@MD1KR9XC.ww002.siemens.net \
--to=christian.storm@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