On Wed, 31 Mar 2021, Greg A. Woods wrote:
Yes I did change that as well (as /var isn't part of the root partition).
I see. How did you change it? Because in 9.99 some things have changed:
rndseed=/var/db/entropy-file
on a line of its own no longer works. You have to attach it to a
On Wed, 31 Mar 2021, Greg A. Woods wrote:
collect and "estimate" _and_ despite the fact there's a valid-looking
$random_file that was saved and reloaded by /etc/rc.d/random_seed (and
saved again every day by /etc/security):
# ls -l /etc/entropy-file
-rw--- 1 root wheel 536 Mar 31 04:15
On Thu, Apr 01, 2021 at 04:13:59AM +, RVP wrote:
> > [...]
>
> Does this /etc/entropy-file match what's there in your /boot.cfg?
irrelevant for Xen, as Xen uses the multiboot protocol.
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
> In this particular example server it's in a Dell R510 with a pair of
> 6-core E5645 CPUs that "cpuid" shows the following for (in the dom0):
this is a westmere-ep CPU, which does not support rdseed
or rdrand. rdrand appeared in ivybridge (2 generations
later, with sandybridge in the middle.)
At Thu, 1 Apr 2021 04:13:59 + (UTC), RVP wrote:
Subject: Re: nothing contributing entropy in Xen domUs? or dom0!!!
>
> Does this /etc/entropy-file match what's there in your /boot.cfg?
>
> On my laptop $random_file is left at the default which is:
> /var/db/entropy-
At Wed, 31 Mar 2021 21:58:48 -0400, Thor Lancelot Simon wrote:
Subject: Re: nothing contributing entropy in Xen domUs? (causing python3.7
rebuild to get stuck in kernel in "entropy" during an "import" statement)
>
> On Wed, Mar 31, 2021 at 11:24:07AM +0200, Manuel Bouyer wrote:
> > On Tue, Mar
