From owner-freebsd-current@FreeBSD.ORG Mon Jun 20 06:36:13 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 43B8116A41C; Mon, 20 Jun 2005 06:36:13 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from pasmtp.tele.dk (pasmtp.tele.dk [193.162.159.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02C0243D53; Mon, 20 Jun 2005 06:36:12 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (0x535c0e2a.sgnxx1.adsl-dhcp.tele.dk [83.92.14.42]) by pasmtp.tele.dk (Postfix) with ESMTP id E9E611EC33A; Mon, 20 Jun 2005 08:36:11 +0200 (CEST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.4/8.13.3) with ESMTP id j5K6a7LK071080; Mon, 20 Jun 2005 08:36:07 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Garance A Drosehn From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 20 Jun 2005 00:51:19 EDT." Date: Mon, 20 Jun 2005 08:36:07 +0200 Message-ID: <71079.1119249367@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: gnn@FreeBSD.org, Robert Watson , current@FreeBSD.org 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, 20 Jun 2005 06:36:13 -0000 In message , Garance A Drosehn writes: >At 10:54 AM +0900 6/20/05, gnn@freebsd.org wrote: >>At Sun, 19 Jun 2005 21:36:03 +0200, >>Poul-Henning Kamp wrote: >> > >>> I'm still not satisfied with the nanobsd config/customize process, >>> ideally I would want to have only a single file with a sensible >> > format control the nanobsd build process. >> >>If I may jump in here. One way to do the build up vs. cut down thing >>is to break up more of the system into understandable chunks, but that >>takes work. Then it's easier to build up a system from components. >> >>I'll take a look at nanonbsd hopefully this week anyways, as I need >>to get it running in a VM as well as on a Soekris at home. I make no >>promises. The last system I worked with that did a componentization >>got it very very wrong. > >Another thing I was thinking about was that we could have more >components which trim themselves down based on #defines for >something like MINIMALIST_USER or MINIMALIST_USERBIN . 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. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.