From owner-freebsd-hackers Mon Jan 1 14:51:20 2001 From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 1 14:51:17 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 662B637B400 for ; Mon, 1 Jan 2001 14:51:16 -0800 (PST) Received: (from uucp@localhost) by ns.internet.dk (8.11.1/8.11.1) with UUCP id f01MpBu05801; Mon, 1 Jan 2001 23:51:11 +0100 (CET) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.11.0/8.11.0) with SMTP id f01Mows18827; Mon, 1 Jan 2001 23:50:59 +0100 (CET) (envelope-from leifn@neland.dk) Message-ID: <04ff01c07445$53563d20$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: "Dan Nelson" Cc: "FreeBSD hackers" References: <2620.978013915@critter> <20001228170241.D404@ringworld.oblivion.bg> <20001228092057.A15343@dan.emsphone.com> Subject: Re: Boot process robustness Date: Mon, 1 Jan 2001 23:45:03 +0100 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > If an fsck fails, ifconfig the interfaces and start an sshd so > > > people can get in remotely and fsck... > > > > What if an fsck on /usr fails? Other than that, I love the idea! > > Force-mount it read-only if necessary, or simply copy a static sshd > into /sbin. Runnning fsck -y is the wrong solution, since if fsck > can't fix an error automatically, something pretty bad has happened > (physical media error, someone dd'ing onto the raw disk, etc).. > Even so, unless the machine contains invaluable data, I guess 99% still does a fsck -y if fsck fails. I'd rather have my remote boxes do that by themselves, and perhaps email me, than I either have to drive there, or give somebody the root password, and remote control that person to just do fsck -y. In almost all cases, when a machine can't fsck itself after a power failure, a fsck -y fixes it. But then, most of the disk is either squid's cache, or unused stuff like termcaps, kernel source, man pages etc. Most stuff is there just because it could be handy one day, and it is not worth the trouble pruning it. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message