Date: Sat, 13 Jan 2001 10:57:26 -0800 (PST) From: Matt Dillon <dillon@earth.backplane.com> To: Mark Murray <mark@grondar.za> Cc: Robert Watson <rwatson@FreeBSD.org>, Warner Losh <imp@harmony.village.org>, 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 Message-ID: <200101131857.f0DIvQR33918@earth.backplane.com> References: <Pine.NEB.3.96L.1010113095651.21474B-100000@fledge.watson.org> <200101131519.f0DFJhI20323@gratis.grondar.za>
next in thread | previous in thread | raw e-mail | index | archive | help
:<repeat iteration=$BIGNUM>
: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.
:</repeat>
:
: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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200101131857.f0DIvQR33918>