From owner-freebsd-arch@FreeBSD.ORG Mon Jul 19 14:14:46 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03DBC16A4CF; Mon, 19 Jul 2004 14:14:46 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5037443D3F; Mon, 19 Jul 2004 14:14:45 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i6JEDtTF028787; Mon, 19 Jul 2004 08:13:55 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 19 Jul 2004 08:13:56 -0600 (MDT) Message-Id: <20040719.081356.51946167.imp@bsdimp.com> To: pjd@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <20040719075952.GG57678@darkness.comp.waw.pl> References: <20040718184008.GC57678@darkness.comp.waw.pl> <20040719.005825.26202805.imp@bsdimp.com> <20040719075952.GG57678@darkness.comp.waw.pl> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: keramida@ceid.upatras.gr cc: zeratul2@wanadoo.es cc: nsouch@free.fr cc: freebsd-arch@FreeBSD.org Subject: Re: some PRs X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2004 14:14:46 -0000 In message: <20040719075952.GG57678@darkness.comp.waw.pl> Pawel Jakub Dawidek writes: : On Mon, Jul 19, 2004 at 12:58:25AM -0600, M. Warner Losh wrote: : +> : Even if it is used by some programms, I don't see it in the base system. : +> : It can be always implemented as a kernel module and maintained outside : +> : the tree. : +> : +> Given that it is implemented in this driver in about 20 lines, I think : +> that it makes sense to have it in the base. Suggesting it be : +> maintained outside of the tree is just plain silly. It should be : +> brought in or abadoned. : : It isn't even used by one of our 11000 ports and you want to bring it : into base system? We don't have other devices in the tree, which are : actually used by some ports. I still think, that if a port which is using : /dev/full will be created, device should be maintained there. : EOT. I guess my point is that that creates so much more work that it seems like overkill. We often put things into the base system for compatibility, but rely on out of system things for higher level functionality. Warner