From owner-freebsd-hackers  Mon Oct 16 22:16:07 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id WAA09711
          for hackers-outgoing; Mon, 16 Oct 1995 22:16:07 -0700
Received: from chrome.jdl.com (chrome.onramp.net [199.1.166.202])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA09705
          for <hackers@FreeBSD.org>; Mon, 16 Oct 1995 22:16:04 -0700
Received: from localhost.jdl.com (localhost.jdl.com [127.0.0.1]) by chrome.jdl.com (8.6.11/8.6.9) with SMTP id XAA04810; Mon, 16 Oct 1995 23:01:43 -0500
Message-Id: <199510170401.XAA04810@chrome.jdl.com>
X-Authentication-Warning: chrome.jdl.com: Host localhost.jdl.com didn't use HELO protocol
To: Bruce Evans <bde@zeta.org.au>
cc: mark@grondar.za, hackers@FreeBSD.org
Subject: Re: Creating a /dev/random 
In-reply-to: Your message of "Tue, 17 Oct 1995 11:23:55 +1000."
             <199510170123.LAA17511@godzilla.zeta.org.au> 
Reply-To: jdl@chromatic.com
Clarity-Index: null
Threat-Level: none
Software-Engineering-Dead-Seriousness: There's no excuse for unreadable code.
Net-thought: If you meet the Buddha on the net, put him in your Kill file.
Date: Mon, 16 Oct 1995 23:01:42 -0500
From: Jon Loeliger <jdl@chrome.onramp.net>
Sender: owner-hackers@FreeBSD.org
Precedence: bulk

Apparently, Bruce Evans scribbled:
> >>I don't understand something here - what happens if the one process is
> >>reading both /dev/zero and /dev/random? will the two not then try to
> >>share buf/zbuf and screw up?
> 
> >See above
> 
> Oops, I misread `one process'.  Well, one process can't be in the kernel
> twice.

...until SMP is implemented and then the whole locking issue
comes into play, right?

jdl