From owner-freebsd-current@FreeBSD.ORG Sat Sep 7 21:31:56 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3B39475; Sat, 7 Sep 2013 21:31:56 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0E52C265E; Sat, 7 Sep 2013 21:31:55 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1VIQ6k-000Alb-Nb; Sat, 07 Sep 2013 21:31:54 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r87LVpUO074929; Sat, 7 Sep 2013 15:31:51 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX19y5kpfFBGXju4RDcs2ExIx Subject: Re: random(4) update causes mips compile fail | mips boot fail From: Ian Lepore To: Mark R V Murray In-Reply-To: <618CA386-7444-4631-A69B-7FD2F22C91E6@grondar.org> References: <1378572186.1588.5.camel@localhost> <24DB010A-F374-491B-9203-FDDD7EA14A51@grondar.org> <1378579011.1588.16.camel@localhost> <9240BEF1-2791-4D58-A422-08AEF1CD306C@grondar.org> <1378586316.1111.524.camel@revolution.hippie.lan> <618CA386-7444-4631-A69B-7FD2F22C91E6@grondar.org> Content-Type: text/plain; charset="us-ascii" Date: Sat, 07 Sep 2013 15:31:51 -0600 Message-ID: <1378589511.1111.529.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Adrian Chadd , "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Sep 2013 21:31:56 -0000 On Sat, 2013-09-07 at 22:25 +0100, Mark R V Murray wrote: > On 7 Sep 2013, at 21:42, Adrian Chadd wrote: > > > We discussed this at the dev summit. Mark asked what we'd like to do. > > > > Mark - would you mind terribly adding a kernel compile option that controls that blocking default, so we can flip it on for the ARM/MIPS boards that don't have a hardware PRNG to start seeding things with? > > This has some merit; but I need to thing about how to do it. Per-architecture block/no-block defaults are going to get messy unless done properly. > > M I think it's fine to default to blocking (make it hard to do the wrong thing by accident), and then any given kernel config can include an OPTION_WHATEVERYOUCALLIT to disable the blocking and let it work the way it does now. Having a tuneable var with a name related to the config option might be nice too, for platforms that can handle such things. Those of us who have to cope with limited systems will fix our config for those systems; that part of it shouldn't be your problem beyond providing us with a knob. -- Ian