From owner-cvs-all  Sat Oct 21  0: 8:15 2000
Delivered-To: cvs-all@freebsd.org
Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229])
	by hub.freebsd.org (Postfix) with ESMTP
	id AFE4C37B4E5; Sat, 21 Oct 2000 00:08:11 -0700 (PDT)
Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1])
	by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9L77rA78008;
	Sat, 21 Oct 2000 00:07:53 -0700 (PDT)
	(envelope-from jkh@winston.osd.bsdi.com)
To: "John W. De Boskey" <jwd@FreeBSD.org>
Cc: "Jordan K. Hubbard" <jkh@FreeBSD.org>,
	cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: Re: cvs commit: src/etc rc 
In-Reply-To: Message from "John W. De Boskey" <jwd@FreeBSD.org> 
   of "Fri, 20 Oct 2000 17:35:57 EDT." <20001020173557.A19403@bsdwins.com> 
Date: Sat, 21 Oct 2000 00:07:52 -0700
Message-ID: <78004.972112072@winston.osd.bsdi.com>
From: Jordan Hubbard <jkh@winston.osd.bsdi.com>
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>    I specifically left the output of dd available so that it
> would be more readily apparent how much data we were seeding
> into /dev/random.  -current isn't supposed to be used by

Well, if you can explain exactly how this information could
also possibly help anyone, I'm happy to see it return. :)

>    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?

Well, my understanding of this from talking to markm is
that it will block until sufficient entropy is available.

- Jordan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message