From owner-freebsd-arch@FreeBSD.ORG Thu Aug 8 21:34:50 2013 Return-Path: Delivered-To: freebsd-arch@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 C350F8FA; Thu, 8 Aug 2013 21:34:50 +0000 (UTC) (envelope-from obrien@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 915CE24C4; Thu, 8 Aug 2013 21:34:50 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r78LYonu081194; Thu, 8 Aug 2013 21:34:50 GMT (envelope-from obrien@freefall.freebsd.org) Received: (from obrien@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r78LYoGi081191; Thu, 8 Aug 2013 21:34:50 GMT (envelope-from obrien) Date: Thu, 8 Aug 2013 14:34:49 -0700 From: "David O'Brien" To: Steve Kargl Subject: Re: random(4) plugin infrastructure for mulitple RNG in a modular fashion Message-ID: <20130808213449.GD95000@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, Steve Kargl , secteam@freebsd.org, freebsd-arch@freebsd.org, Arthur Mesh References: <20130807182858.GA79286@dragon.NUXI.org> <20130807192736.GA7099@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130807192736.GA7099@troutmask.apl.washington.edu> X-Operating-System: FreeBSD 10.0-CURRENT X-MUA-Host: dragon.NUXI.org X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Arthur Mesh , secteam@freebsd.org, freebsd-arch@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 21:34:50 -0000 On Wed, Aug 07, 2013 at 12:27:36PM -0700, Steve Kargl wrote: > On Wed, Aug 07, 2013 at 11:28:58AM -0700, David O'Brien wrote: > > * Make Yarrow an optional kernel component -- enabled by "YARROW_RNG" > > option. The files sha2.c, hash.c, randomdev_soft.c and yarrow.c .. > My kernel config files have included the following 2 lines for > ages: > makeoptions NO_MODULES > device random > > If I try to build a new kernel under your scheme, will the > build die with an error about a missing option? You haven't given enough information to answer the question. Your kernel config does not have just those two lines. Is there an "include GENERIC" or something else above it? What is your full kernel config? > If the answer > is 'no', then the yarrow adaptor should be opt-out. There is no build issue (i.e., missing symbols). "device random" in the changeset is just the device (/dev/[u]random) implimentation. The many RNG's that provide the output. Do you really not read UPDATING and the release notes when you upgrade to to a .0 release? How did you learn about other config lines I'm sure you've changed over th years. e.g., options GEOM_PART_*, options SCHED_ULE, options NFSCL, options NFSD, any of the new gigE NIC's added over the past decade, removal of device ata & device atadisk, and removal of non-locked/MPSAFE drivers are things I can think of that you've likely added(removed) to your config over time. Lack of some of those would not cause a build break or config warning, but would have resulted in a less functional kernel. -- -- David (obrien@FreeBSD.org)