From owner-freebsd-current@FreeBSD.ORG Wed Nov 19 21:28:19 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 83B4A16A4CE for ; Wed, 19 Nov 2003 21:28:19 -0800 (PST) Received: from kientzle.com (h-66-166-149-50.SNVACAID.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C80543FF7 for ; Wed, 19 Nov 2003 21:28:18 -0800 (PST) (envelope-from kientzle@acm.org) Received: from acm.org ([66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id hAK5RukX028299; Wed, 19 Nov 2003 21:27:56 -0800 (PST) (envelope-from kientzle@acm.org) Message-ID: <3FBC50DB.3000002@acm.org> Date: Wed, 19 Nov 2003 21:27:55 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006 X-Accept-Language: en-us, en MIME-Version: 1.0 To: richardcoleman@mindspring.com 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> In-Reply-To: <3FBC29EF.3030009@mindspring.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: dyson@iquest.net cc: masta@wifibsd.org cc: Dan Nelson cc: current@freebsd.org cc: imp@bsdimp.com Subject: Re: Unfortunate dynamic linking for everything X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kientzle@acm.org 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 05:28:19 -0000 Richard Coleman wrote: > It seems /bin/sh is the real sticking point. There is a problem here: Unix systems have historically used /bin/sh for two somewhat contradictory purposes: * the system script interpreter * as a user shell The user shell must be dynamically linked in order to support centralized administration. I personally see no way around that. Given that many users do rely on /bin/sh, it seems that /bin/sh must be dynamically linked. There are good reasons to want the system script interpreter statically linked. Maybe it's time to separate these two functions? I would be content to have a static /sbin/sh that is used as the system script interpreter for rc scripts, etc. Tim Kientzle