From owner-cvs-all Sat Jan 13 10:58:20 2001 Delivered-To: cvs-all@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id D5D9A37B400; Sat, 13 Jan 2001 10:57:54 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0DIvQR33918; Sat, 13 Jan 2001 10:57:26 -0800 (PST) (envelope-from dillon) Date: Sat, 13 Jan 2001 10:57:26 -0800 (PST) From: Matt Dillon Message-Id: <200101131857.f0DIvQR33918@earth.backplane.com> To: Mark Murray Cc: Robert Watson , Warner Losh , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc crontab rc src/etc/defaults rc.conf src/etc/mtree BSD.root.dist src/libexec Makefile src/libexec/save-entropy Makefile save-entropy.sh References: <200101131519.f0DFJhI20323@gratis.grondar.za> Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :When the high-rate harvesters go in (after the preemptive threading), :the "off" --> "on" transition will happen within a couple of seconds, :and will no longer be a problem. : : :M :-- :Mark Murray This isn't good enough. What if the devices the high-rate harvesters use aren't configured in the system? You need to *guarentee* that the boot sequence will not block. Can you guarentee that your high rate harvesters, in every possible configuration of the system, will be able to unblock /dev/random in a few seconds? If you can *guarentee* that the boot sequence doesn't stall for more then a few seconds, in any OS config, then I'm fine with the blocking /dev/random. If you can't guarentee it, then it isn't a robust enough solution. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message