From owner-freebsd-hackers  Mon Nov 25 21:17:32 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id VAA09650
          for hackers-outgoing; Mon, 25 Nov 1996 21:17:32 -0800 (PST)
Received: from everest.dtr.com (livdial5.fta.com [205.139.102.199])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA09586
          for <hackers@FreeBSD.org>; Mon, 25 Nov 1996 21:16:40 -0800 (PST)
Received: (from bmk@localhost) by everest.dtr.com (8.8.2/8.6.12) id VAA01010; Mon, 25 Nov 1996 21:11:28 -0800 (PST)
Message-Id: <199611260511.VAA01010@everest.dtr.com>
Subject: Re: A simple way to crash your system.
To: nate@mt.sri.com (Nate Williams)
Date: Mon, 25 Nov 1996 21:11:13 -0800 (PST)
Cc: jkh@time.cdrom.com, ben@narcissus.ml.org, kjk1@ukc.ac.uk,
        hackers@FreeBSD.org
In-Reply-To: <199611260208.TAA02586@rocky.mt.sri.com> from Nate Williams at "Nov 25, 96 07:08:10 pm"
From: "Brant M. Katkansky" <bmk@fta.com>
Reply-To: bmk@fta.com
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
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

> > > Msdosfs is seriously broken.  It has twice damaged my filesystem to the 
> > > extent that I had to reinstall FreeBSD.  Don't use it.
> > 
> > We should probably just remove it entirely for now.  I have some
> > stand-alone dosfs reading code which Robert Nordier gave me and I
> > intend to use for sysinstall, so that's that case covered.  Otherwise,
> > as you've already found out, you take your life in your hands with
> > msdosfs.

> I use it all the time, but I'm *very* careful not to run more than one
> process on the FS, and I unmount the darn thing as soon as I read/write
> the files to the FS.

> It works as long as I treat it like fragile china, and not having it
> would be a real setback for me.

"Me too."

I treat mine more or less the same as Nate, and I have never had a
problem.  I would hate to see it go away, but I think it'd be reasonable
to warn novice users in the documentation (or do we already?).