From owner-freebsd-arch@FreeBSD.ORG Thu Jul 17 01:08:09 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1937937B401 for ; Thu, 17 Jul 2003 01:08:09 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DEB143FE3 for ; Thu, 17 Jul 2003 01:08:08 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.9/8.12.9) with ESMTP id h6H885ju099234 for ; Thu, 17 Jul 2003 01:08:06 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.9/8.12.9/Submit) id h6H885NE099233 for freebsd-arch@freebsd.org; Thu, 17 Jul 2003 01:08:05 -0700 (PDT) Date: Thu, 17 Jul 2003 01:08:05 -0700 From: "David O'Brien" To: freebsd-arch@freebsd.org Message-ID: <20030717080805.GA98878@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.1-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Subject: Things to remove from /rescue X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-arch@freebsd.org List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 08:08:09 -0000 This is a list of binaries that I don't feel should be part of /resuce as it's mission is to recover/rebuild a "broken" / [due to all the binaries being dynamic]. Is there justification for keeping them? - domainname, one does not need YP in the circumstances /rescue is meant to address. - date, one can use a watch if they really want to know it is 5am and their system is down. - sleep, this is what the admin wishes he was doing at 5am rather than trying to recover a borked system. The admin doesn't need the OS sleeping and delaying the repair. - adjkerntz, who cares if the date is wrong if you right to the FS (and you are on a PC and have Winloose on it also). At the least this should only be installed on i386. - comcontrol, I can't begin to imagine why one would need this to fix a borked /. - conscontrol, I can't begin to imagine why one would need this to fix a borked /. - growfs, how would growing / fix a borked /lib?? - ipfw & natd & ipf & ipfs & ipfstat & ipmon & ipnan, why would one needs these? /rescue is to fix a borked /, not replace PicoBSD. - nfsiod, to quote "It improves performance but is not required for correct operation." Recovering a borked / doesn't need to be high performance. - quotacheck, does one really want to enforce quota's on root, while he is trying direly to fix a borked /?? - shutdown, 'reboot' is sufficient when single user -- there are no other users on the system inform of the impending shutdown. - swapon, this is not needed to fix a whacked out /lib.... unless we add Emacs to /resuce. - wall, when single user (as one needs to be to fix a broked /) who is one going to communicate with?? - tar, pax (w/{bz,g}zip) can do everything GNU tar can.