svn commit: r346250 - in head: share/man/man4 share/man/man9 sys/dev/random sys/kern sys/libkern sys/sys

[Justin Hibbits]

Hi Conrad,

On Mon, 15 Apr 2019 17:53:17 -0700
Conrad Meyer <cem at freebsd.org> wrote:

> Hi Justin,
> 
> On Mon, Apr 15, 2019 at 5:01 PM Justin Hibbits <chmeeedalf at gmail.com>
> wrote:
> > Given the discussion over there it would probably also fail on
> > powernv, which also does not use loader.  
> 
> Does power use bsdinstall (which populates /boot/entropy at install
> time via usr.sbin/bsdinstall/scripts/entropy) and install the
> libexec/rc/rc.d/random rc script (which re-emits new /boot/entropy on
> every startup)?  If so, it should be ok.
> 
> The problem is new installs that don't use bsdinstall or otherwise
> provide initial /boot/entropy.  E.g., the CI infrastructure for
> Riscv/Arm is/was generating minimal filesystem images and not
> populating /boot/entropy.
> 
> Best,
> Conrad

It does use bsdinstall to install.  How is entropy loaded at startup,
which causes the problem noted in github?  If it's loaded before
filesystems get mounted, that could be a problem for us, because /boot
is on a different filesystem (msdosfs, to be read by petitboot).
Petitboot also does not have a way to preload modules, so all we have
at startup, until spawning init, is the kernel.

- Justin