From owner-freebsd-current Wed Mar 29 11:28:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA26837 for current-outgoing; Wed, 29 Mar 1995 11:28:43 -0800 Received: from irbs.com ([199.182.75.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA26819 for ; Wed, 29 Mar 1995 11:28:38 -0800 Received: (from jc@localhost) by irbs.com (8.6.11/8.6.6) id OAA19400 for freebsd-current@freefall.cdrom.com; Wed, 29 Mar 1995 14:28:25 -0500 From: John Capo Message-Id: <199503291928.OAA19400@irbs.com> Subject: Re: chflags should be compiled static To: freebsd-current@freefall.cdrom.com (freebsd-current) Date: Wed, 29 Mar 1995 14:28:24 -0500 (EST) In-Reply-To: <9503291907.AA10409@olympus> from "Boyd Faulkner" at Mar 29, 95 01:07:31 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 768 Sender: current-owner@FreeBSD.org Precedence: bulk Boyd Faulkner writes: > > I had a merry adventure. On a make world, I got a corrupted libc.so.2.1. > Needless to say, the phrase ld.so failed became very familiar to me, very > quickly. > > Unfortunately, libc.so.2.1 is installed with the schg option. I was unable > to remove the offending library as I could not disable this option because > chflags said ld.so failed. ld.so is similarly locked down. I managed > to get around this by moving the directory and copying the needed libraries > into the new /usr/lib. This should be avoided by making this tools static. > Reasoning: If I have to use the tool to fix the library, the tool should > not depend on the library. And put it in /sbin or /bin please. I recently did similar handstands. -- John Capo