From owner-freebsd-current Mon Jun 26 10:25:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 2DBEA37BC25; Mon, 26 Jun 2000 10:25:26 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id OAA01050; Mon, 26 Jun 2000 14:09:45 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200006261209.OAA01050@grimreaper.grondar.za> To: obrien@freebsd.org Cc: dfr@freebsd.org, freebsd-current@freebsd.org Subject: Re: HEADS UP! New (incomplete) /dev/random device! References: <20000626020538.F14265@dragon.nuxi.com> In-Reply-To: <20000626020538.F14265@dragon.nuxi.com> ; from "David O'Brien" "Mon, 26 Jun 2000 02:05:39 MST." Date: Mon, 26 Jun 2000 14:09:45 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Jun 25, 2000 at 12:35:12PM +0200, Mark Murray wrote: > > 3) It is not built by default (except as a kernel module), so you > > either need to add the "options RANDOMDEV" like to your kernel > > config, or load it at boot time in /dev/loader.conf > > Can't things be made to autoload random.ko as happens for if_fxp.ko when > I ifconfig it, or msdos.ko and procfs.ko when I mount them. I'd like to do this, but there is no "trigger" that can be hooked to do the work (mount and ifconfig can both do the work, but where do you hook a read(2) from /dev/random?) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message