From owner-freebsd-small Wed Jul 3 11:45:38 2002 Delivered-To: freebsd-small@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A0EA37B400 for ; Wed, 3 Jul 2002 11:45:35 -0700 (PDT) Received: from jupiter.linuxengine.net (jupiter.linuxengine.net [209.61.188.254]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE2E843E09 for ; Wed, 3 Jul 2002 11:45:34 -0700 (PDT) (envelope-from john@utzweb.net) Received: from jupiterweb.commercevault.com (jupiterweb.commercevault.com [209.61.179.16] (may be forged)) by jupiter.linuxengine.net (8.11.6/8.11.0) with ESMTP id g63IjGR05696; Wed, 3 Jul 2002 13:45:16 -0500 Date: Wed, 3 Jul 2002 13:45:16 -0500 (CDT) From: John Utz X-X-Sender: john@jupiter.linuxengine.net To: Darren Pilgrim Cc: W Gerald Hicks , Subject: Re: Guide to reducing FreeBSD (a.k.a miniBSD :) In-Reply-To: <3D229963.EF2B40B3@pantherdragon.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 2 Jul 2002, Darren Pilgrim wrote: > W Gerald Hicks wrote: > > > > On Wednesday, July 3, 2002, at 12:10 AM, Darren Pilgrim wrote: > > [snips] > > > As long as you realize that if a /bin or /sbin program can't run due > > > to missing/corrupt libraries that you may or may not be able to even > > > boot single-user. At the very least, /bin/sh, /sbin/mount, /sbin/init, > > > and /sbin/fsck should be static builds. > > > > > > > Libraries residing in a linked-in MD_ROOT_IMAGE are available whenever > > the kernel is > > but it still seems more space efficient for that small handful of > > critical files to be crunch-linked. > > Those libraries can still get corrupted. Using dynamic binaries adds > a point of failure. It's not much more space taken for just those few > programs, so why increase the risk? ahh, because this is where we cross into the land of the manufactuing world :-) when you are designing a commodity product, cost reduction is key. if you have a choice of shrinking the OS and getting it onto a cheaper part, you will. If i have a us$1.00 memory device that will contain the image iff i link dynamically, and i have a us$1.05 part that is twice as big that will allow me to use the safer statically linked bits, then i will have a long and hard discussion about this during the design review. If i can come up with a rational, value adding, *marketable* use for all my new empty space, i might be able to win the argument. If the part only costs us$0.01 more, instead of us$0.05 more, than i can probably get the part blessed with no argument and somebody else will own the job of figuring out how to use that extra space in a future product improvement. If the part costs us$0.25 more, i wont even waste my breath. :-) Tho i will include a paragraph about the issue in my design doc. > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-small" in the body of the message > -- John L. Utz III john@utzweb.net Idiocy is the Impulse Function in the Convolution of Life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message