From owner-freebsd-hackers Sun Mar 19 12:25:38 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA21743 for hackers-outgoing; Sun, 19 Mar 1995 12:25:38 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA21731 for ; Sun, 19 Mar 1995 12:25:36 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id MAA24478; Sun, 19 Mar 1995 12:24:56 -0800 From: Poul-Henning Kamp Message-Id: <199503192024.MAA24478@ref.tfs.com> Subject: Re: Filesystem clean flag To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 19 Mar 1995 12:24:56 -0800 (PST) Cc: davidg@Root.COM, Remy.Card@masi.ibp.fr, hackers@FreeBSD.org In-Reply-To: <199503192005.VAA15103@uriah.heep.sax.de> from "J Wunsch" at Mar 19, 95 09:05:06 pm Content-Type: text Content-Length: 581 Sender: hackers-owner@FreeBSD.org Precedence: bulk > As David Greenman wrote: > > > > The system should not allow mounting a dirty filesystem writable. > > But then, there should also be a way to get around this. The super > user is assumed to know what he's doing -- and be it for the only > reason to save just one [apparently good] file out of a totally > damaged disk before newfs'ing it. Why would he need to mount it writeable for that ? -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant'