From owner-cvs-all Sun Oct 22 22:13: 1 2000 Delivered-To: cvs-all@freebsd.org Received: from grimreaper.grondar.za (adsl-63-206-96-212.dsl.snfc21.pacbell.net [63.206.96.212]) by hub.freebsd.org (Postfix) with ESMTP id B898C37B4CF; Sun, 22 Oct 2000 22:12:57 -0700 (PDT) Received: from grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.1/8.11.1) with ESMTP id e9N5Cpa08139; Sun, 22 Oct 2000 22:12:52 -0700 (PDT) (envelope-from mark@grondar.za) Message-Id: <200010230512.e9N5Cpa08139@grimreaper.grondar.za> To: "John W. De Boskey" Cc: "Jordan K. Hubbard" , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc rc References: <20001020173557.A19403@bsdwins.com> In-Reply-To: <20001020173557.A19403@bsdwins.com> ; from "John W. De Boskey" "Fri, 20 Oct 2000 17:35:57 EDT." Date: Sun, 22 Oct 2000 22:12:51 -0700 From: Mark Murray Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message