Re: download_dev-random hook question

[Alexander Smirnov <asmirnov@ilbers.de>]

Hi,

On 11/16/2017 12:41 PM, 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.
> 
> 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 :)
> 

Will you handle this? :-) Or I could add it to TODO?

Alex