public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: "[ext] Jan Kiszka" <jan.kiszka@siemens.com>,
	Alexander Smirnov <asmirnov@ilbers.de>,
	Baurzhan Ismagulov <ibr@radix50.net>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] Install /dev/null in rootfs
Date: Tue, 30 Jan 2018 12:44:17 +0100	[thread overview]
Message-ID: <20180130124417.130d5b4c@mmd1pvb1c.ad001.siemens.net> (raw)
In-Reply-To: <14fbc8f0-b5dd-afd0-bd73-1592f6ee05ca@siemens.com>

Good catch,

but that and the other mknods makes we wonder why wo do not just
bind-mount /dev. And while we are at it also /sys.

/dev /proc and /sys are known to be usually required for a working
system. Is there a reason to not just mount all three of them?
Otherwise it seems like this patch is just another one in a long series
of mknod patches.

Henning

Am Tue, 30 Jan 2018 10:31:21 +0100
schrieb "[ext] Jan Kiszka" <jan.kiszka@siemens.com>:

> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> ...or hell breaks loose, at least in the buildchroot:
> 
> x86 kernel builds will generate strange modules.order/builtin files.
> That's because drivers/firmware/Makefile does
> $(call as-instr,.arch armv7-a\n.arch_extension sec,-DREQUIRES_SEC=1)
> That tries the above assembly on the x86 gcc which will not understand
> it and complain. It's output is directed to /dev/null, but that does
> not exist, so it will be printed to the above modules.* files. Argh.
> 
> Who knows what may happen in the image rootfs, so update it as well.
> Which reminds us that this ugly duplication should be resolved ASAP.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>  .../files/{download_dev-random => download_dev-nodes}       |  7
> +++++++ meta-isar/recipes-core/images/isar-image-base.bb
> |  4 ++-- meta/recipes-devtools/buildchroot/buildchroot.bb
> |  4 ++-- .../recipes-devtools/buildchroot/files/download_dev-nodes
> |  7 +++++++
> meta/recipes-devtools/buildchroot/files/download_dev-random | 13
> ------------- 5 files changed, 18 insertions(+), 17 deletions(-) copy
> meta-isar/recipes-core/images/files/{download_dev-random =>
> download_dev-nodes} (73%) rename
> meta-isar/recipes-core/images/files/download_dev-random =>
> meta/recipes-devtools/buildchroot/files/download_dev-nodes (73%)
> delete mode 100644
> meta/recipes-devtools/buildchroot/files/download_dev-random
> 
> diff --git a/meta-isar/recipes-core/images/files/download_dev-random
> b/meta-isar/recipes-core/images/files/download_dev-nodes similarity
> index 73% copy from
> meta-isar/recipes-core/images/files/download_dev-random copy to
> meta-isar/recipes-core/images/files/download_dev-nodes index
> f7f5fe5..3149faa 100644 ---
> a/meta-isar/recipes-core/images/files/download_dev-random +++
> b/meta-isar/recipes-core/images/files/download_dev-nodes @@ -7,6
> +7,13 @@ set -e 
>  readonly ROOTFS="$1"
>  
> +if [ ! -c ${ROOTFS}/dev/null ]; then
> +    rm -f ${ROOTFS}/dev/null
> +    mknod "${ROOTFS}/dev/null" c 1 3
> +    chmod 666 "${ROOTFS}/dev/null"
> +    chown 0:0 "${ROOTFS}/dev/null"
> +fi
> +
>  if [ ! -c ${ROOTFS}/dev/random ]; then
>      rm -f ${ROOTFS}/dev/random
>      mknod "${ROOTFS}/dev/random" c 1 8
> diff --git a/meta-isar/recipes-core/images/isar-image-base.bb
> b/meta-isar/recipes-core/images/isar-image-base.bb index
> 2f03cd1..3954697 100644 ---
> a/meta-isar/recipes-core/images/isar-image-base.bb +++
> b/meta-isar/recipes-core/images/isar-image-base.bb @@ -12,7 +12,7 @@
> FILESPATH =. "${LAYERDIR_isar}/recipes-core/images/files:" SRC_URI =
> "file://multistrap.conf.in \ file://${DISTRO_CONFIG_SCRIPT} \
>  	   file://setup.sh \
> -	   file://download_dev-random"
> +	   file://download_dev-nodes"
>  
>  PV = "1.0"
>  
> @@ -38,7 +38,7 @@ do_rootfs() {
>  
>      chmod +x "${WORKDIR}/${DISTRO_CONFIG_SCRIPT}"
>      chmod +x "${WORKDIR}/setup.sh"
> -    install -m 755 "${WORKDIR}/download_dev-random"
> "${WORKDIR}/hooks_multistrap/"
> +    install -m 755 "${WORKDIR}/download_dev-nodes"
> "${WORKDIR}/hooks_multistrap/" 
>      # Multistrap accepts only relative path in configuration files,
> so get it: cd ${TOPDIR}
> diff --git a/meta/recipes-devtools/buildchroot/buildchroot.bb
> b/meta/recipes-devtools/buildchroot/buildchroot.bb index
> 51f9d5d..8743a02 100644 ---
> a/meta/recipes-devtools/buildchroot/buildchroot.bb +++
> b/meta/recipes-devtools/buildchroot/buildchroot.bb @@ -12,7 +12,7 @@
> FILESPATH =. "${LAYERDIR_core}/recipes-devtools/buildchroot/files:"
> SRC_URI = "file://multistrap.conf.in \ file://configscript.sh \
>             file://setup.sh \
> -           file://download_dev-random \
> +           file://download_dev-nodes \
>             file://build.sh"
>  PV = "1.0"
>  
> @@ -39,7 +39,7 @@ do_build() {
>  
>      chmod +x "${WORKDIR}/setup.sh"
>      chmod +x "${WORKDIR}/configscript.sh"
> -    install -m 755 "${WORKDIR}/download_dev-random"
> "${WORKDIR}/hooks_multistrap/"
> +    install -m 755 "${WORKDIR}/download_dev-nodes"
> "${WORKDIR}/hooks_multistrap/" 
>      # Multistrap accepts only relative path in configuration files,
> so get it: cd ${TOPDIR}
> diff --git a/meta-isar/recipes-core/images/files/download_dev-random
> b/meta/recipes-devtools/buildchroot/files/download_dev-nodes
> similarity index 73% rename from
> meta-isar/recipes-core/images/files/download_dev-random rename to
> meta/recipes-devtools/buildchroot/files/download_dev-nodes index
> f7f5fe5..3149faa 100644 ---
> a/meta-isar/recipes-core/images/files/download_dev-random +++
> b/meta/recipes-devtools/buildchroot/files/download_dev-nodes @@ -7,6
> +7,13 @@ set -e 
>  readonly ROOTFS="$1"
>  
> +if [ ! -c ${ROOTFS}/dev/null ]; then
> +    rm -f ${ROOTFS}/dev/null
> +    mknod "${ROOTFS}/dev/null" c 1 3
> +    chmod 666 "${ROOTFS}/dev/null"
> +    chown 0:0 "${ROOTFS}/dev/null"
> +fi
> +
>  if [ ! -c ${ROOTFS}/dev/random ]; then
>      rm -f ${ROOTFS}/dev/random
>      mknod "${ROOTFS}/dev/random" c 1 8
> diff --git
> a/meta/recipes-devtools/buildchroot/files/download_dev-random
> b/meta/recipes-devtools/buildchroot/files/download_dev-random deleted
> file mode 100644 index 5b5b96b..0000000 ---
> a/meta/recipes-devtools/buildchroot/files/download_dev-random
> +++ /dev/null @@ -1,13 +0,0 @@
> -#!/bin/sh
> -
> -set -e
> -
> -readonly ROOTFS="$1"
> -
> -mknod "${ROOTFS}/dev/random" c 1 8
> -chmod 640 "${ROOTFS}/dev/random"
> -chown 0:0 "${ROOTFS}/dev/random"
> -
> -mknod "${ROOTFS}/dev/urandom" c 1 9
> -chmod 640 "${ROOTFS}/dev/urandom"
> -chown 0:0 "${ROOTFS}/dev/urandom"


  reply	other threads:[~2018-01-30 11:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30  9:31 Jan Kiszka
2018-01-30 11:44 ` Henning Schild [this message]
2018-02-02 10:41   ` Jan Kiszka
2018-02-02 12:19   ` Alexander Smirnov
2018-02-02 12:35     ` Jan Kiszka

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=20180130124417.130d5b4c@mmd1pvb1c.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=asmirnov@ilbers.de \
    --cc=ibr@radix50.net \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@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