Date: Sat, 13 Jan 2001 17:15:11 -0800 (PST) From: Matt Dillon <dillon@earth.backplane.com> To: Peter Wemm <peter@netplex.com.au> Cc: Doug Barton <DougB@FreeBSD.org>, 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: <200101140115.f0E1FBU36854@earth.backplane.com> References: <200101140026.f0E0QEQ86706@mobile.wemm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
:Did you hack up your custom kernel config to add 'options DEVRANDOM'?
:Obviously you found out about that option somehow, so the same process
:should lead you to the NOBLOCKRANDOM option.
:
:Cheers,
:-Peter
DEVRANDOM is as broken as everything else. It doesn't make the pain
disappear if it isn't there. Does it stop the cron job from starting
up? No. Is it sufficient to test -w for DEVRANDOM-config'd kernels
in /etc/rc? No. Does it prevent the save-entropy script from running?
No. So much for DEVRANDOM!
The /dev/random commits have created problem after problem, incrementally
and in whole. And unncessarily. One sysctl is all it would have taken
to test for their enablement in the scripts, and one sysctl is all it
would take to have an opt-in rc.conf variable to turn it on. It hasn't
happened yet.
What I am asking for here is reasonable: Cleanup this stuff so it is
entirely opt-in for the developers, based on an rc.conf variable which
defaults to off. It can't be that difficult.
-Matt
:--
:Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au
:"All of this is for nothing if we don't go to the stars" - JMS/B5
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?200101140115.f0E1FBU36854>