Re: download_dev-random hook question

[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?
> >
> 
> 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.

Ah, I see... I totally agree.

> 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.

Yes, we're on the same page here, agreed.

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

Even without the switch, I do find the explicit variant, well, more explicit :)


Besten Gru�,
   Christian

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