From owner-freebsd-hackers Fri Oct 16 19:40:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15380 for freebsd-hackers-outgoing; Fri, 16 Oct 1998 19:40:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15357 for ; Fri, 16 Oct 1998 19:40:14 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id TAA16560; Fri, 16 Oct 1998 19:39:48 -0700 (PDT) (envelope-from jdp) Message-Id: <199810170239.TAA16560@austin.polstra.com> To: ncb05@uow.edu.au Subject: Re: random data for operations in kernel In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Date: Fri, 16 Oct 1998 19:39:48 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Nicholas Charles Brawn wrote: > What do people suggest would be the best way to derive a random value > for use in a system call? Are there any examples in the present kernel > source tree that perform this, or a similar operation? Sys/libkern has "random.c" with a function random(). Elsewhere there's the code implementing /dev/random. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message