From owner-freebsd-hackers Mon Mar 20 14:35:36 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA10515 for hackers-outgoing; Mon, 20 Mar 1995 14:35:36 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA10509 for ; Mon, 20 Mar 1995 14:35:33 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id OAA27099; Mon, 20 Mar 1995 14:35:25 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id OAA02339; Mon, 20 Mar 1995 14:35:24 -0800 Message-Id: <199503202235.OAA02339@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: Stephen McKay cc: hackers@FreeBSD.org Subject: Re: Filesystem clean flag In-reply-to: Your message of "Mon, 20 Mar 95 19:27:18 +1000." <199503200927.TAA15395@orion.devetir.qld.gov.au> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 20 Mar 1995 14:35:23 -0800 Sender: hackers-owner@FreeBSD.org Precedence: bulk >David Greenman writes; >>>> 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 ? >> >> Yes, this is why I said "writable" above. I would always want read-only to >>work. ...but like I just said in a previous message, an option to force the >>system to mount writable it wouldn't be unreasonable. > >If you don't provide this option, I'll just have to add it. Certainly a I should mention here that I don't intend to work on this before 2.1R. If people want the problem with mouting dirty filesystems to be handled better in 2.1R, then someone other than me needs to make these changes and send them to me. I'm far too busy dealing with kernel issues at the moment. -DG