Date: Tue, 21 Mar 1995 07:47:36 +0100 (MET) From: J Wunsch <j@uriah.heep.sax.de> To: syssgm@devetir.qld.gov.au (Stephen McKay) Cc: hackers@FreeBSD.org, syssgm@devetir.qld.gov.au Subject: Re: Filesystem clean flag Message-ID: <199503210647.HAA24319@uriah.heep.sax.de> In-Reply-To: <199503200927.TAA15395@orion.devetir.qld.gov.au> from "Stephen McKay" at Mar 20, 95 07:27:18 pm
next in thread | previous in thread | raw e-mail | index | archive | help
As Stephen McKay wrote: > > > 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 As i think more about it, option `-f' (perhaps in conjunction with `-w') could still be used for this. It's otherwise only used to force just the opposite (revoke write access when downgrading from r/w to r/o), but the idea to `force' something does apply as well. (-f -r -> force r/o, -f -w -> force r/w) > BTW, does anyone have any disk-cruising/filesystem-fixing programs that are > friendlier than fsck? My 1.1 system went mad and overwrote every root > directory and their superblocks and a good number of other (apparently) random > blocks. I think I upset my tape drive while reading past EOD... Well, i've just added `fsdb(8)' to the TODO list a few days ago. D'ya know somebody who can implement it? ;-) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503210647.HAA24319>