From owner-freebsd-current Sun Nov 3 13:23:52 2002 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 4763D37B401 for ; Sun, 3 Nov 2002 13:23:51 -0800 (PST) Received: from HAL9000.homeunix.com (12-232-220-15.client.attbi.com [12.232.220.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B05743E4A for ; Sun, 3 Nov 2002 13:23:50 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id gA3LNaC4052392; Sun, 3 Nov 2002 13:23:36 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id gA3LNREB052391; Sun, 3 Nov 2002 13:23:27 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Sun, 3 Nov 2002 13:23:27 -0800 From: David Schultz To: Miguel Mendez Cc: Wesley Morgan , kientzle@acm.org, current@FreeBSD.ORG Subject: Re: libc size Message-ID: <20021103212327.GA52281@HAL9000.homeunix.com> Mail-Followup-To: Miguel Mendez , Wesley Morgan , kientzle@acm.org, current@FreeBSD.ORG References: <3DC17C7F.9020308@acm.org> <20021031140542.W86715-100000@volatile.chemikals.org> <20021031220633.3acd0b53.flynn@energyhq.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021031220633.3acd0b53.flynn@energyhq.homeip.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Miguel Mendez : > Why? I'd love to hear some real reasons for this. NetBSD-current has > just gone fully dynamic, let's see how much space that needs... > > christine: {16} uname -srnm > NetBSD christine.energyhq.tk 1.6J i386 > christine: {17} du -h /bin /sbin /lib > 999K /bin > 1.7M /sbin > 2.0M /lib > > /lib keeps the required shared libs for those programs residing in > /[s]bin. > > IMHO it would be beneficial to, at least, have the option to build a > fully dynamic system on FreeBSD. Keep in mind that NetBSD's /bin and /sbin were significantly smaller beforehand. FreeBSD's equivalent is somewhat bloated, but it's not so unreasonably large that people are having trouble making it fit on hard drives purchased in the last four years. If you're installing FreeBSD on an embedded system, that's one thing, but you have PicoBSD for that. Otherwise, you're sacrificing performance, reliability, and security for the sake of a few dozen megs of disk space. I don't think this is an acceptable tradeoff. I'm not opposed to having a knob that allows people to dynamically link their /bin and /sbin if they so desire, as long as it's done right. I worry a little bit that once the feature is available, someone will decide that it's a bright idea to turn it on by default, and support for the static linking case will decline. (This is similar to what happened with GEOM, although I happen to be all in favor of the latter. C'est la vie.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message