From: Henning Schild <henning.schild@siemens.com>
To: "[ext] [ext] Christian Storm" <christian.storm@siemens.com>
Cc: <isar-users@googlegroups.com>
Subject: Re: download_dev-random hook question
Date: Mon, 20 Nov 2017 10:41:38 +0100 [thread overview]
Message-ID: <20171120104138.42466b1d@md1em3qc> (raw)
In-Reply-To: <20171116090453.pkret232zz6kxi23@MD1KR9XC.ww002.siemens.net>
Am Thu, 16 Nov 2017 10:04:53 +0100
schrieb "[ext] [ext] Christian Storm" <christian.storm@siemens.com>:
> > 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 [...]
>
> ... and, a further question that just came to my mind: Why is this
> handled in a multistrap hook in the first place? Seems rather
> implicit to me. Why not do it explicitly in buildchroot.bb and
> isar-image-base.bb?
Is a hook not explicit? I do not get the point. Using a script outside
of do_build even allows for sharing between the two users. And these two
recipes should probably be deduplicated one day.
Henning
>
> Besten Gruß,
> Christian
>
next prev parent reply other threads:[~2017-11-20 9:41 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
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 [this message]
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=20171120104138.42466b1d@md1em3qc \
--to=henning.schild@siemens.com \
--cc=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