public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Alexander Smirnov <asmirnov@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: download_dev-random hook question
Date: Thu, 16 Nov 2017 12:19:27 +0300	[thread overview]
Message-ID: <276a3671-4986-633b-0c28-e47a63a8e2e6@ilbers.de> (raw)
In-Reply-To: <20171116090453.pkret232zz6kxi23@MD1KR9XC.ww002.siemens.net>

Hi,

On 11/16/2017 12:04 PM, [ext] Christian Storm wrote:
>> 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?
>

IIRC correctly multistrap configuration was taken from Debian/Embian 
examples. So I'd personally prefer to drop all the hooks and make 
necessary calls explicitly in recipes.

So I see it like the following:
  - recipe creates rootfs, mounts necessary folders and creates device 
files.
  - recipe calls multistrap which only downloads the packages and unpack 
them to rootfs.
  - recipe calls configscript which performs post-configuration for rootfs.

This would be very helpful in context of switching to debootstrap.

Alex

  reply	other threads:[~2017-11-16  9:19 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 [this message]
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=276a3671-4986-633b-0c28-e47a63a8e2e6@ilbers.de \
    --to=asmirnov@ilbers.de \
    --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