Date: Mon, 23 Oct 2000 08:15:48 -0400 From: "John W. De Boskey" <jwd@FreeBSD.org> To: Mark Murray <mark@grondar.za> Cc: "Jordan K. Hubbard" <jkh@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc rc Message-ID: <20001023081548.A41843@bsdwins.com> In-Reply-To: <200010230512.e9N5Cpa08139@grimreaper.grondar.za>; from mark@grondar.za on Sun, Oct 22, 2000 at 10:12:51PM -0700 References: <20001020173557.A19403@bsdwins.com> <200010230512.e9N5Cpa08139@grimreaper.grondar.za>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Mark Murray's Original Message ----- > > Depends on your definition of block... Yes, it could go > > in the background, but what if the system finished booting > > and a request to /dev/random occurs before the seeding is > > finished? > > It would wait for the reseed, then continue... > > > ps: On a side note, I'm seeing some interaction on a machine > > with an mfs and /dev/random. I haven't tracked it down > > yet, but why would an mfs require input from /dev/random? > > (this is occurring at boot time). > > ldconfig? No, see my previous mail concerning FSIRAND. The mfs code in newfs/mount_mfs requires random number generation. Not sure how to fix it (chick 'n egg condition). -John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001023081548.A41843>