From owner-freebsd-current@FreeBSD.ORG Mon Jul 4 08:23:54 2005 Return-Path: X-Original-To: current@freebsd.org 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 183C716A41C; Mon, 4 Jul 2005 08:23:54 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECF9F43D53; Mon, 4 Jul 2005 08:23:53 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (proxy7.corp.yahoo.com [216.145.48.98]) by mrout1.yahoo.com (8.13.4/8.13.4/y.out) with ESMTP id j648MCmU002828; Mon, 4 Jul 2005 01:22:12 -0700 (PDT) Date: Mon, 04 Jul 2005 10:00:28 +0900 Message-ID: From: gnn@freebsd.org To: "Poul-Henning Kamp" In-Reply-To: <71079.1119249367@critter.freebsd.dk> References: <71079.1119249367@critter.freebsd.dk> User-Agent: Wanderlust/2.12.2 (99 Luftballons) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.2 (powerpc-apple-darwin) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: gnn@freebsd.org, Robert Watson , current@freebsd.org, Garance A Drosehn Subject: Re: Summary: experiences with NanoBSD, successes and nits on a Soekris 4801 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 04 Jul 2005 08:23:54 -0000 At Mon, 20 Jun 2005 08:36:07 +0200, Poul-Henning Kamp wrote: > The trouble with options like this is that they escape our normal > build tests. > > A good example of this is the kernel option INET which in theory > is optional, but which on average only is it 10% of the time. The only way to get this to work, IMHO, is to take the full system, and generate a dependency graph, if that's even possible. Then you know where to cut and where new APIs need to be defined to know where to cut. I'll try to generate this as part of the scripts on code-speluking.org. Later, George