From owner-freebsd-current@FreeBSD.ORG Mon Nov 24 07:49:51 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 DAF6E16A4CE for ; Mon, 24 Nov 2003 07:49:51 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C50C743FDD for ; Mon, 24 Nov 2003 07:49:50 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9p2/8.12.9) with ESMTP id hAOFlPMg085332; Mon, 24 Nov 2003 10:47:25 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)hAOFlONN085329; Mon, 24 Nov 2003 10:47:25 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 24 Nov 2003 10:47:24 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Maxim M. Kazachek" In-Reply-To: <20031124092346.F63116@sbk-gw.sibnet.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org cc: Duncan Barclay Subject: Re: Unfortunate dynamic linking for everything X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2003 15:49:52 -0000 On Mon, 24 Nov 2003, Maxim M. Kazachek wrote: > MOST people uses /bin/sh only for rc scripts (to be correct, their > system uses it). David O'Brien just tried to told, that NOBODY he knows > will be REALLY impacted by performance loss, caused due dynamic /bin/sh > linking. You will... So, because Duncan Barclay is impacted by > performance loss due dynamic /bin/sh linking, ENTIRE FreeBSD community > will have troubles (at least with NSS) due to static linking... Actually, you appear to be agreeing with him, not disagreeing with him. Duncan was pointing out that he *does* use /bin/sh as his shell, in response to David's suggestion that on one uses it and therefore that making it statically linked wouldn't hurt. It strikes me that this whole conversation has gotten a little confrontational... The "middle ground" of adding a static /sbin/sh for scripts soudds like a reasonable choice, and has precedent in other systems (Solaris). We can set the boot and periodic scripts to use that, and interactive users can keep using /bin/sh. Someone must be using /bin/sh as a shell, because apparently someone spent a lot of time adding things like character input editing, filename completion, etc. We even use "sh" as the default in adduser(8). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories