From owner-freebsd-current Fri Mar 9 10:41: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 97C9637B718; Fri, 9 Mar 2001 10:40:58 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA22988; Fri, 9 Mar 2001 10:40:48 -0800 Date: Fri, 9 Mar 2001 10:40:45 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mark Murray , Kris Kennaway Cc: current@freebsd.org Subject: Re: Entropy harvesting? Grim reaper is more like it... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I commented out all of the Entropy stuff at the front of rc and I was able to finish booting again. I'll do another buildworld/installworld and buildkernel/installkernel to see whether the problem re-appears. I'll leave the 'set -x' in my rc when I retest. I noticed the (re)appearance of a line which had caused problems in the past (the 'ps' generation foo). I'd really appreciate if the following would occur: 1. The entropy stuff gets it's own rc file. There's a lot of it. 2. You make it an option we can turn off sourcing it from rc. Also- we should really consider whether or not the breakage that has happened three or four times now is telling us something. This attempt to reseed entropy seems to be riskier than not having the entropy reseeded at all! :-) If this entropy stuff is all that important, maybe we should consider having this done entirely within the kernel as part of the config state tree (and not as a kmod or an option) so that a simple non-blocking sysctl early in RC can get you what you want. That is, by the time you call /sbin/init, you have gathered enough entropy. Or if you cannot do so (which I would imagine could actually be a true statement as all I/O results are *generally* pretty predictable until you turn on networking), can you do it *after* the system is almost all the way up? I guess I'm saying I don't want to have to get hung up like this any more. Please. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message