tag 787989 - moreinfo
retitle 787989 add native hook to create /dev/random for jessie support
thanks

On Sun, 07 Jun 2015 18:44:10 +0200
Johannes Schauer <jo...@debian.org> wrote:

> Quoting Neil Williams (2015-06-07 18:31:07)
> > It might be worth investigating whether the jessie / stretch
> > chroots can be configured manually and what steps are required to
> > do so.
> > 
> > In the absence of information on what multistrap could actually have
> > done and why packages in sid "just work", there isn't much that can
> > be done with this report.
> 
> adding a hook which adds /dev/random and /dev/urandom before package
> configuration fixes this problem.
> 
> Is this the info you were asking for?

Yes, absolutely. Thanks.
 
> In a maybe related note: after filing this bug I also saw the
> configuration of openssh-server fail because of a
> missing /dev/random. But I'm sure this used to work earlier (about
> half a year ago) as I was
> calling /usr/share/multistrap/device-table.pl in my setupscript and
> at least in the past that used to be enough (and I don't think that
> openssh-server did not require /dev/random to generate its private
> keys in the past).  Was the point at which setupscripts are executed
> maybe changed in one of the recent multistrap releases?

The actual multistrap script has not changed substantially since the
version in Jessie - some extra support scripts were removed and a patch
was applied for apt's Etc::Dir directive support.

> Anyway, both my problems are now fixed by creating the respective
> device nodes in a native hook before configuration.

Thanks, I'll look at a default hook for jessie (or an example hook to
add /dev/random to any suite) at that point.

-- 


Neil Williams
=============
http://www.linux.codehelp.co.uk/

Attachment: pgpTdOW15jfXj.pgp
Description: OpenPGP digital signature

Reply via email to