From owner-freebsd-questions Mon Aug 28 3: 1:15 2000 Delivered-To: freebsd-questions@freebsd.org Received: from giroc.albury.net.au (giroc.albury.NET.AU [203.15.244.13]) by hub.freebsd.org (Postfix) with ESMTP id 74A9D37B43C for ; Mon, 28 Aug 2000 03:01:08 -0700 (PDT) Received: (from nicks@localhost) by giroc.albury.net.au (8.9.3/8.9.3) id VAA49746; Mon, 28 Aug 2000 21:01:00 +1100 (EST) Date: Mon, 28 Aug 2000 21:01:00 +1100 From: Nick Slager To: "A. Yahya Sjarifuddin." Cc: freebsd-questions@FreeBSD.ORG Subject: Re: fsck Message-ID: <20000828210100.B46808@albury.net.au> References: <39AA33F5.F765CDC6@cbn.net.id> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39AA33F5.F765CDC6@cbn.net.id>; from yahya@cbn.net.id on Mon, Aug 28, 2000 at 04:42:13PM +0700 X-Homer: Whoohooooooo! Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake A. Yahya Sjarifuddin. (yahya@cbn.net.id): > Dear All, > If there's someting happened with the harddisk, > i.e crash, sudden power down etc. how could I > bypass fsck routine during booting? You don't want to do this. The filesystem is in an unknown state after a powerfail, and an fsck is essential to correct any problems. Writing to the disk on a dirty filesystem is just asking for trouble :-) Nick. -- From a Sun Microsystems bug report (#4102680): "Workaround: don't pound on the mouse like a wild monkey." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message