From owner-freebsd-current@FreeBSD.ORG Mon Jun 20 04:51:23 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 BBC1E16A41C; Mon, 20 Jun 2005 04:51:23 +0000 (GMT) (envelope-from gad@FreeBSD.org) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CD6943D48; Mon, 20 Jun 2005 04:51:23 +0000 (GMT) (envelope-from gad@FreeBSD.org) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp4.server.rpi.edu (8.13.0/8.13.0) with ESMTP id j5K4pK9l022187; Mon, 20 Jun 2005 00:51:21 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: References: <20050619155228.Y6413@fledge.watson.org> <66959.1119209763@critter.freebsd.dk> Date: Mon, 20 Jun 2005 00:51:19 -0400 To: gnn@FreeBSD.org, "Poul-Henning Kamp" From: Garance A Drosehn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) on 128.113.2.4 Cc: 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 04:51:23 -0000 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 . I almost tried that with the recent changes to `env', for instance. The new options I added are very nice, but they do add something like 20%-40% to the size of the executable. And someone putting together a minimal system could easily avoid writing scripts that need the new options. If a user could set one #define to cause all programs in /usr/bin to shrink by 10-15%, that might be valuable. Not sure we could get that much, or if we would want to support that idea as time goes on. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy, NY; USA