From owner-cvs-all Sat Jan 13 16:25: 0 2001 Delivered-To: cvs-all@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 2DC6537B402; Sat, 13 Jan 2001 16:24:38 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0E0Nb161132; Sat, 13 Jan 2001 16:23:37 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200101140007.f0E07G336509@earth.backplane.com> Date: Sat, 13 Jan 2001 16:24:38 -0800 (PST) From: John Baldwin To: Matt Dillon Subject: Re: cvs commit: src/etc crontab rc src/etc/defaults rc.conf src/ Cc: cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org, Robert Watson , Mark Murray , Doug Barton Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Jan-01 Matt Dillon wrote: > >: >: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. > > That is not an appropriate stopgap. It fixes NOBODY who config's up > custom kernels unless they know about the option and hack up their > configs. Forcing people to hack up their configs is not a stopgap. Umm, Matt. If you are buildiong a custom config, it is customary to start from GENERIC. If you are updating from a really old current, then you should know by now that looking at the updates to GENERIC is a very good bullet-in-foot saving exercise. Also, you know, we hashed this out on the mailing lists like months ago (which is where the NOBLOCKRANDOM thing came from). Where were you? Secondly, this is _-current_. Add the option to your kernel and get over it. There are lots of other more productive things that need to be done. In fact, SMPng could _really_ benefit from having the VM system locked down, since most parts of the kernel end up migrating into VM at some point in time, and for us to be able to move part of the kernel out from under Giant, we have to ensure that everything below that portion is locked and MP safe. Hopefully, you can see the obvious benefits. Thirdly, slow down and calm down. From the volume of mail this thread is consuming right now, it has descended into blue-in-the-face arguing back and forth where both sides are dug in and on the defensive, neither willing to back down for the sake of pride. Please, go take a break. Continuing with emotional rants that keep going back and forth does not change anyone's mind. However, it does lower your esteem in the minds of the spectators. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message