From owner-freebsd-current@FreeBSD.ORG Sun Nov 16 18:24:05 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 3929616A4CE for ; Sun, 16 Nov 2003 18:24:05 -0800 (PST) Received: from kakapo.santafe.edu (kakapo.santafe.edu [192.12.12.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3276A43FD7 for ; Sun, 16 Nov 2003 18:24:04 -0800 (PST) (envelope-from brent@santafe.edu) Received: from [10.0.1.2] (pcp04161662pcs.sntafe01.nm.comcast.net [68.35.42.183]) (authenticated bits=0) by kakapo.santafe.edu (8.12.10/8.12.10) with ESMTP id hAH2O1DK011502 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Sun, 16 Nov 2003 19:24:03 -0700 (MST) Mime-Version: 1.0 (Apple Message framework v606) In-Reply-To: <3FB7A44C.1000002@mindspring.com> References: <20031116051028.GA30485@roark.gnf.org> <3FB7A44C.1000002@mindspring.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <1AAE62E6-18A5-11D8-B9A8-000393652EF2@santafe.edu> Content-Transfer-Encoding: 7bit From: Brent Jones Date: Sun, 16 Nov 2003 19:24:00 -0700 To: current@freebsd.org X-Mailer: Apple Mail (2.606) X-Filter-Version: 1.14 (kakapo) Subject: Re: HEADS UP: /bin and /sbin are now dynamically linked 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, 17 Nov 2003 02:24:05 -0000 On Nov 16, 2003, at 9:22 AM, Richard Coleman wrote: > Robert M.Zigweid wrote: >> I'll admit to being mostly a lurker here, but isn't the point of >> /sbin to be statically linked. That's what the 's' stands for? >> Second question. This seems to imply that /sbin and /bin both have >> to have the same behavior? I have no problem with /bin being >> dynamically linked, but what if I want /bin to be dynamic and /sbin >> static? >> Regards, >> Robert M. Zigweid > > I'm not sure what that would accomplish. If a system was broken such > that the dynamically linked binaries in /bin didn't work, the > utilities in /sbin wouldn't be enough to fix the system. For > instance, you wouldn't have a shell or "ls". This is just a case of OS evolution. /sbin used to be the place where the statically linked recovery things would be placed, in case the shared libraries got hosed. The only things that needed to be statically linked though, were system utilities, which is why people probably started to associate the "s" with system, rather than static. When this happened, you started to see the duplicates that used to exist in /bin (or /usr/bin) and /sbin disappear. Since you still need a place to have statically linked recovery utilities, /rescue was created. Now you see the duplicates in /bin (or /usr/bin) and /rescue instead. Brent