From owner-freebsd-current@FreeBSD.ORG Mon Nov 24 20:53:26 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 9BBA516A4CE; Mon, 24 Nov 2003 20:53:26 -0800 (PST) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DB0343F85; Mon, 24 Nov 2003 20:53:24 -0800 (PST) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])hAOJ9Gf1075535; Tue, 25 Nov 2003 06:09:16 +1100 (EST) (envelope-from jeremyp@cirb503493.alcatel.com.au) Received: (from jeremyp@localhost)hAOJ9F0g075534; Tue, 25 Nov 2003 06:09:15 +1100 (EST) (envelope-from jeremyp) Date: Tue, 25 Nov 2003 06:09:15 +1100 From: Peter Jeremy To: Rahul Siddharthan Message-ID: <20031124190915.GG39616@cirb503493.alcatel.com.au> References: <20031124114006.GA60761@dragon.nuxi.com> <20031124160024.GA27996@online.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031124160024.GA27996@online.fr> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org cc: Tim Kientzle 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: Tue, 25 Nov 2003 04:53:26 -0000 On Mon, Nov 24, 2003 at 11:00:24AM -0500, Rahul Siddharthan wrote: >David O'Brien wrote: >> On Sun, Nov 23, 2003 at 06:00:36PM -0800, Tim Kientzle wrote: >> > Scenarios that require /rescue are ones in which /bin and /sbin >> > are unusable, which is almost always going to imply a trashed file >> > in /bin, /sbin, or /lib. Thus, most /rescue scenarios are going to >> > involve locating a good copy of a trashed file to replace a damaged >> > local copy. >> >> NO. /rescue was allowed in the system to handle the case of a trashed >> file in /lib[exec]. To allow a sysadmin to recover a system from the >> same type of mishaps they could before we went to a dynamic /. > >Ie, let's do things the same way we did in 1994? To put it another way. FreeBSD has never had the ability to recover from a hosed root or /usr using FTP, though you can use rrestore or rcp to recover /usr. There has never been a great groundswell of complaints about this (offhand, I can't recall any). Why does this suddenly become a major issue once / is dynamically linked? > Other things have >changed since then, hard drives and typical root partitions are much >bigger, Pre-existing harddrives and root partitions do not magically expand over time. A new installation and/or a new harddrive might have a much bigger root partition but an existing one won't. > and Tim estimated the total bloat from this as 64k. And then someone else wants their favourite tool which is only another 64K and so on. Pretty soon you have a 200MB /rescue. > Maybe >earlier, pre-/rescue, you couldn't recover from damaged files in the >root partition without a CD/floppy/NFS, it doesn't mean you should not >have that capability in /rescue. If no-one's missed it in the past, why would they suddenly need it now? Peter