From owner-freebsd-current@FreeBSD.ORG  Sun Nov 23 15:26:52 2003
Return-Path: <owner-freebsd-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 535CC16A4CE
	for <current@freebsd.org>; Sun, 23 Nov 2003 15:26:52 -0800 (PST)
Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net
	[207.217.120.189])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 423CE43F85
	for <current@freebsd.org>; Sun, 23 Nov 2003 15:26:51 -0800 (PST)
	(envelope-from richardcoleman@mindspring.com)
Received: from titan.criticalmagic.com ([68.213.16.23] helo=mindspring.com)
	by heron.mail.pas.earthlink.net with asmtp (Exim 3.33 #1)
	id 1AO3cw-0002IN-00; Sun, 23 Nov 2003 15:26:50 -0800
Message-ID: <3FC14245.6030509@mindspring.com>
Date: Sun, 23 Nov 2003 18:27:01 -0500
From: Richard Coleman <richardcoleman@mindspring.com>
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: current@freebsd.org
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> <3FBC29EF.3030009@mindspring.com>
	<3FBC50DB.3000002@acm.org> <20031123225117.GA24696@dragon.nuxi.com>
In-Reply-To: <20031123225117.GA24696@dragon.nuxi.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 1ee258965991efcb0865379cdb43356e5e89bb4777695beb702e37df12b9c9ef9e6c74b41ee89a714e64a1c135f487c1350badd9bab72f9c350badd9bab72f9c
cc: masta@wifibsd.org
cc: Dan Nelson <dnelson@allantgroup.com>
cc: imp@bsdimp.com
cc: dyson@iquest.net
cc: Tim Kientzle <kientzle@acm.org>
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Nov 2003 23:26:52 -0000

David O'Brien wrote:
> We should build /bin/sh static and be done with the argument.
> Or rather, lets find a /bin/sh interactive user and have him argue that
> /bin/sh needs NSS support.  I dare say that will be a thread two orders
> of magnitude shorter than this one.

Statically linking /bin/sh wouldn't be that big a deal.  It would be 
trivial to add a port to compile a dynamic version of sh for customers 
that *really* want sh.  Personally, I can't remember a customer 
specifically requesting that.

You would need to make sure that startup scripts never use tilde 
expansion.  I'm not sure how common that is with RCNG.

But it would be sorta odd to have statically linked versions of sh in 
both /bin and /rescue.

Richard Coleman
richardcoleman@mindspring.com