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?
> 
> Is a hook not explicit? I do not get the point. 

It depends :)

In my opinion it's not explicit as /dev node generation is kind of a
side-effect of running multistrap realized via its hooks. If multistrap
would have done it anyway without us placing the hook in there, fine.
But we're placing a hook script in multistrap that does the work -
which could as well be done in do_build(), there named explicitly as
/dev node generation. If I wanted to know how/where /dev node generation
is done, there's as of now one more indirection in terms of the
multistrap hook. That said, I'm not strongly opinionated on this as I
guess it's mostly a matter of taste though...


> Using a script outside of do_build even allows for sharing between the
> two users. 

Yes, but this is also true if this external script is called from within
the two do_builds, explicitly.


> And these two recipes should probably be deduplicated one day.

Yes, I agree but that's another issue...



   Christian

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