From owner-freebsd-arch@FreeBSD.ORG Thu Jul 17 09:13:21 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 2E88637B401; Thu, 17 Jul 2003 09:13:21 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4617343F3F; Thu, 17 Jul 2003 09:13:12 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.9/8.12.3) with ESMTP id h6HGDBFL006879; Thu, 17 Jul 2003 10:13:11 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 17 Jul 2003 10:13:06 -0600 (MDT) Message-Id: <20030717.101306.97372251.imp@bsdimp.com> To: freebsd-arch@freebsd.org, obrien@freebsd.org From: "M. Warner Losh" In-Reply-To: <20030717080805.GA98878@dragon.nuxi.com> References: <20030717080805.GA98878@dragon.nuxi.com> X-Mailer: Mew version 2.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Things to remove from /rescue X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list 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 16:13:21 -0000 In message: <20030717080805.GA98878@dragon.nuxi.com> "David O'Brien" writes: : - domainname, one does not need YP in the circumstances /rescue is meant : to address. I'd agree of its marginality. : - date, one can use a watch if they really want to know it is 5am and : their system is down. Setting the time/date can be important at times, so keeping this would be good. : - 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. agreed. : - 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. agreed, since this is needed only at the DST transitions. : - comcontrol, I can't begin to imagine why one would need this to fix : a borked /. agreed. : - conscontrol, I can't begin to imagine why one would need this to fix : a borked /. agreed. : - growfs, how would growing / fix a borked /lib?? this could be useful, but it is definitely at the margin. : - ipfw & natd & ipf & ipfs & ipfstat & ipmon & ipnan, why would one needs : these? /rescue is to fix a borked /, not replace PicoBSD. agreed. : - nfsiod, to quote "It improves performance but is not required for : correct operation." Recovering a borked / doesn't need to be high : performance. agreed. : - quotacheck, does one really want to enforce quota's on root, while he : is trying direly to fix a borked /?? could be useful to repair borked quotas on /, but it is at the margins. : - shutdown, 'reboot' is sufficient when single user -- there are no other : users on the system inform of the impending shutdown. agreed. : - swapon, this is not needed to fix a whacked out /lib.... unless we add : Emacs to /resuce. This is also marginal, but might be needed. : - wall, when single user (as one needs to be to fix a broked /) who is : one going to communicate with?? agreed. : - tar, pax (w/{bz,g}zip) can do everything GNU tar can. agreed, but there should be links to it. Basically, all the ones I marked as marginal are small enough to include w/o a large impact. A quick ls suggests that they would only add about 32k to the image, which seems reasonable. the others, well, we can save the space. Warner