From owner-freebsd-current@FreeBSD.ORG Mon May 19 12:21:24 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C314837B404; Mon, 19 May 2003 12:21:24 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92D7D43F75; Mon, 19 May 2003 12:21:23 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.9/8.12.9) with ESMTP id h4JJLJA9006476; Mon, 19 May 2003 12:21:23 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.9/8.12.9/Submit) id h4JJLJhh006475; Mon, 19 May 2003 12:21:19 -0700 (PDT) Date: Mon, 19 May 2003 12:21:19 -0700 From: "David O'Brien" To: Ruslan Ermilov Message-ID: <20030519192119.GA4267@dragon.nuxi.com> Mail-Followup-To: David O'Brien , Ruslan Ermilov , re@FreeBSD.org, current@FreeBSD.org References: <3EC825C4.6040203@btc.adaptec.com> <20030519024518.05B402A7EA@canning.wemm.org> <20030519061401.GB40604@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030519061401.GB40604@sunbay.com> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: re@FreeBSD.org cc: current@FreeBSD.org Subject: Re: Tidying src/release/*/{dokern.sh,drivers.conf} X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: re@FreeBSD.org, current@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2003 19:21:25 -0000 On Mon, May 19, 2003 at 09:14:01AM +0300, Ruslan Ermilov wrote: > I can see the point in having only a module, but then > I could say I was confused by sparc64/GENERIC which > has both. sparc64/GENERIC was the old-man out. I feel we should return {i386,alpha,ia64}/GENERIC back to their previous way of no ispfw since this is quite late in the 5.1 game to be changing this. I then think we should ponder making sparc64 consistent with {i386,alpha,ia64}/GENERIC. -- -- David (obrien@FreeBSD.org)