From owner-cvs-all Mon Oct 23 5:16:46 2000 Delivered-To: cvs-all@freebsd.org Received: from bsdone.bsdwins.com (www.bsdwins.com [192.58.184.33]) by hub.freebsd.org (Postfix) with ESMTP id 0C11E37B479; Mon, 23 Oct 2000 05:16:42 -0700 (PDT) Received: (from jwd@localhost) by bsdone.bsdwins.com (8.11.0/8.11.0) id e9NCFnj41861; Mon, 23 Oct 2000 08:15:49 -0400 (EDT) (envelope-from jwd) Date: Mon, 23 Oct 2000 08:15:48 -0400 From: "John W. De Boskey" To: Mark Murray Cc: "Jordan K. Hubbard" , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc rc Message-ID: <20001023081548.A41843@bsdwins.com> References: <20001020173557.A19403@bsdwins.com> <200010230512.e9N5Cpa08139@grimreaper.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200010230512.e9N5Cpa08139@grimreaper.grondar.za>; from mark@grondar.za on Sun, Oct 22, 2000 at 10:12:51PM -0700 Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- 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