From owner-freebsd-current@FreeBSD.ORG Mon Nov 24 18:27:16 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 7127116A4CE; Mon, 24 Nov 2003 18:27:16 -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 E204F43FE0; Mon, 24 Nov 2003 18:27:14 -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 hAP2REkX049485; Mon, 24 Nov 2003 18:27:14 -0800 (PST) (envelope-from kientzle@acm.org) Message-ID: <3FC2BE01.1040807@acm.org> Date: Mon, 24 Nov 2003 18:27:13 -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: <3FBE8D92.6080205@acm.org> <20031123012222.GB11523@dragon.nuxi.com> <20031123042635.GB677@saboteur.dek.spc.org> <3FC16644.7070005@acm.org> <20031124114006.GA60761@dragon.nuxi.com> <3FC2655A.8080202@acm.org> <20031124224030.GB67578@dragon.nuxi.com> <3FC298E9.1050000@acm.org> <3FC2B3C1.4090803@mindspring.com> In-Reply-To: <3FC2B3C1.4090803@mindspring.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org 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 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: Tue, 25 Nov 2003 02:27:16 -0000 X-List-Received-Date: Tue, 25 Nov 2003 02:27:16 -0000 X-List-Received-Date: Tue, 25 Nov 2003 02:27:16 -0000 Richard Coleman wrote: > I think a better compromise is to add the make.conf option so that extra > utilities may be added to /rescue. As David already pointed out, this is not entirely trivial. Adding the programs isn't difficult, but it requires adjusting library includes, which would be tricky to do automatically. In addition, a surprising number of programs require minor source edits to function correctly in /rescue. In particular, many programs have hard-coded references to specific programs in /bin and /sbin. I spent a long time tracking down such references and replacing them with references to /rescue where appropriate. Without those changes, /rescue will work correctly only if /bin and /sbin are functional. There is a real potential for landmines here. > With the size of disk drives these days, (for my own setup) I'm tempted > to just add a complete copy of /bin and /sbin into /rescue. There's surprisingly little of /bin and /sbin that isn't already in /rescue. Most of what's omitted was left out for very straightforward reasons (e.g., tcsh is clearly redundant, devd is incompatible with crunchgen, etc.) The debate right now is over what programs from /usr/bin and /usr/sbin should be included. Right now, that includes tar, gzip, bzip2, and vi/ex. Tim Kientzle