Date: Sat, 13 Jan 2001 15:46:30 -0800 From: Doug Barton <DougB@FreeBSD.org> To: Matt Dillon <dillon@earth.backplane.com> Cc: Mark Murray <mark@grondar.za>, Robert Watson <rwatson@FreeBSD.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: <3A60E8D6.6E7E3281@FreeBSD.org> References: <200101132228.f0DMSN135897@earth.backplane.com> <200101132237.f0DMbbI21558@gratis.grondar.za> <200101132251.f0DMpKS36028@earth.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Matt Dillon wrote:
> If we are going to have to wait, then please commit a stopgap
That stopgap was committed 10/27/00 in the form of the NOBLOCKRANDOM
kernel config option which is the default in GENERIC. With this option
enabled you will guarantee that /dev/random never blocks, including at boot
time.
> -- Warner's preloading patch, for example.
Which, as has already been explained about 3 different times now will not
cause /dev/random to unblock because it does not generate anywhere near
enough entropy.
> There is absolutely no reason to leave the
> tree in a broken state this long.
The tree is not broken. There are numerous ways for you to avoid ever
having to deal with this issue until the code is more polished, and in the
case of the above mentioned option, the default would mean that you would
never see it in the first place. What's more, everything we have at this
point _works_. The fact that you don't like the way it works does not mean
it's broken.
> Do you really think it is appropriate to commit something to the tree that
> blows developers up (on top of something that is already blowing developers
> up), then spend a week debating how to do it right without either
> (a) backing out the commit or (b) committing a stopgap workaround
> while you debate the issue?
Well, I agree that the debate has been for the most part unproductive,
especially when you continue to demand in loud, belligerent tones that we
do things we've already agreed should be done and/or are already available.
If you don't want to deal with the issues related to the random device
right now you have it within your power to go with the defaults and turn it
off. Please try to restrain yourself from further comment for at least a
couple weeks while we continue to polish what we have. If we could spend
less time answering e-mail and more time coding, the polish will happen
sooner. :)
Doug
--
"The most difficult thing in the world is to know how to do a thing and
to watch someone else do it wrong without comment."
-- Theodore H. White
Do YOU Yahoo!?
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?3A60E8D6.6E7E3281>