From owner-freebsd-hackers Mon Nov 4 17:47:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA20189 for hackers-outgoing; Mon, 4 Nov 1996 17:47:57 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA20183 for ; Mon, 4 Nov 1996 17:47:53 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id MAA20974 for hackers@freebsd.org; Tue, 5 Nov 1996 12:17:42 +1030 From: Michael Smith Message-Id: <199611050147.MAA20974@genesis.atrad.adelaide.edu.au> Subject: fsck for embedded systems? To: hackers@freebsd.org Date: Tue, 5 Nov 1996 12:17:42 +1030 (CST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk One I've been waiting to be bitten by for a while has finally come up; How do people out there building embedded BSD systems get around the fact that fsck won't take -p and -y simultaneously? ie. if you have an untidy shutdown, and the system comes up with a slightly unhappy disk, what's the best way of dealing with this? -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[