Hi, 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? 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? Anyway, both my problems are now fixed by creating the respective device nodes in a native hook before configuration. Maybe you want to add a jessie.conf with the right hook to multistrap just as there is a sid.conf because I imagine that multistrap-ing Jessie might be desired by more people than just me until Stretch is released? Thanks! cheers, josch
signature.asc
Description: signature
