Date: Fri, 20 Oct 2000 17:35:57 -0400 From: "John W. De Boskey" <jwd@FreeBSD.org> To: "Jordan K. Hubbard" <jkh@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc rc Message-ID: <20001020173557.A19403@bsdwins.com> In-Reply-To: <200010201741.KAA87475@freefall.freebsd.org>; from jkh@FreeBSD.org on Fri, Oct 20, 2000 at 10:41:46AM -0700 References: <200010201741.KAA87475@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
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
the general 'user', so I wasn't real worried about the
output (it wasn't/isn't permanent).
As to backgrounding...
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?
-John
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).
----- Jordan K. Hubbard's Original Message -----
> jkh 2000/10/20 10:41:46 PDT
>
> Modified files:
> etc rc
> Log:
> Redirect the stderr of dd to /dev/null so the user doesn't see rather
> weird dd output on bootup as /dev/random is being reseeded. Also,
> can't this happen in the background since /dev/random blocks?
>
> Revision Changes Path
> 1.238 +3 -3 src/etc/rc
>
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?20001020173557.A19403>