public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "[ext] Christian Storm" <christian.storm@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: download_dev-random hook question
Date: Tue, 14 Nov 2017 10:06:45 +0100	[thread overview]
Message-ID: <20171114090645.qni3p5iq3iqtuurb@MD1KR9XC.ww002.siemens.net> (raw)
In-Reply-To: <20171113190916.2193e849@md1em3qc>

> [...]
> Christian, you patched it to shrink it. Did you try removing that step?

Nope, and I'd like to extend that step in terms of /dev/ nodes to be
created instead of removing it :)

> I can just guess that nodes will be created by packages/hooks and
> something in multistrap needs certain nodes before that happens.

Yes, a subset of the standard ones (TM) are required, i.e.,
/dev/{null,{u,}random,...}, you name it.

So, I'd like to have a static /dev/ setup in such a way that the
essential files required to boot are present, even without udev or the
like having created them dynamically.
To be precise, I'd like a to-be-renamed download_dev-random to include
  mknod -m 666 /dev/null c 1 3
  mknod -m 666 /dev/zero c 1 5
  mknod -m 666 /dev/random c 1 8
  mknod -m 666 /dev/urandom c 1 9
  mkdir -m 755 /dev/pts
  mkdir -m 1777 /dev/shm
  mknod -m 666 /dev/tty c 5 0
  mknod -m 600 /dev/console c 5 1
  mknod -m 666 /dev/tty0 c 4 0
  mknod -m 666 /dev/full c 1 7
  mknod -m 600 /dev/initctl p
  mknod -m 666 /dev/ptmx c 5 2


Besten Gru�,
   Christian

-- 
Dr. Christian Storm
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Otto-Hahn-Ring 6, 81739 M�nchen, Germany

  reply	other threads:[~2017-11-14  9:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-13 16:35 Christian Storm
2017-11-13 18:09 ` Henning Schild
2017-11-14  9:06   ` [ext] Christian Storm [this message]
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=20171114090645.qni3p5iq3iqtuurb@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