From owner-freebsd-current@FreeBSD.ORG Wed Nov 19 18:44:43 2003 Return-Path: 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 AE9B816A4CE for ; Wed, 19 Nov 2003 18:44:43 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E5C843FA3 for ; Wed, 19 Nov 2003 18:44:42 -0800 (PST) (envelope-from richardcoleman@mindspring.com) Received: from titan.criticalmagic.com ([68.213.16.23] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (Exim 3.33 #1) id 1AMenX-0003yM-00; Wed, 19 Nov 2003 18:43:59 -0800 Message-ID: <3FBC29EF.3030009@mindspring.com> Date: Wed, 19 Nov 2003 21:41:51 -0500 From: Richard Coleman Organization: Critical Magic, Inc. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dan Nelson References: <62981.24.0.61.35.1069202574.squirrel@mail.yazzy.org> <200311190103.hAJ13Nlg000923@dyson.jdyson.com> <20031119015433.GN30485@roark.gnf.org> <3FBC2053.6040208@mindspring.com> <20031120022009.GB29530@dan.emsphone.com> In-Reply-To: <20031120022009.GB29530@dan.emsphone.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: 1ee258965991efcb0865379cdb43356e5e89bb4777695beb702e37df12b9c9ef5a43beb788df26ac2da26f6142356b68350badd9bab72f9c350badd9bab72f9c cc: imp@bsdimp.com cc: masta@wifibsd.org cc: current@freebsd.org cc: dyson@iquest.net Subject: Re: Unfortunate dynamic linking for everything X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: richardcoleman@mindspring.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Nov 2003 02:44:43 -0000 Dan Nelson wrote: > In the last episode (Nov 19), Richard Coleman said: > >>I don't really care whether everything is statically or dynamically >>linked. With the fast machines and huge disks these days, bloat is not >>much of an issue. But nss and pam need to work correctly. If the folks >>that are against dynamic linking have an alternate method to make this >>work, I'm all for it. But it needs to be more than theory. We need code. >> >>To be honest, I've never understood the (seemingly irrational) >>resistance against this change. Solaris made this change 10 years ago. > > > Not completely: > > $ uname -a > SunOS pd1 5.9 Generic_112233-08 sun4u sparc SUNW,Ultra-Enterprise > $ file /bin/sh > /sbin/sh: ELF 32-bit MSB executable SPARC Version 1, statically linked, stripped > $ file /sbin/* | grep statically | cut -d: -f1 | fmt > /sbin/autopush /sbin/fdisk /sbin/jsh /sbin/mount /sbin/sh > /sbin/soconfig /sbin/sync /sbin/umount /sbin/uname I have no problem with FreeBSD doing something similar and leaving a few binaries static. I think most of the resistance to that was due to the increased complexity of the build system. It seems /bin/sh is the real sticking point. But if the compromise is to statically link /bin/sh, that would be cool with me. Other than tilde expansion not working when using nss_ldap, I can't think of any other problems. I consider that a minor blemish I could easily live with. Normal users will not generally have /bin/sh has their shell anyways. And I could always compile a dynamically linked version into /usr/bin if necessary. To be honest, 98% of the time that someone notices brokeness due to nss_ldap, it comes when using /bin/ls. Richard Coleman richardcoleman@mindspring.com