From owner-freebsd-hackers  Mon Nov 25 17:04:57 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id RAA24420
          for hackers-outgoing; Mon, 25 Nov 1996 17:04:57 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA24352
          for <hackers@FreeBSD.org>; Mon, 25 Nov 1996 17:03:55 -0800 (PST)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.2/8.6.9) with ESMTP id RAA08486; Mon, 25 Nov 1996 17:03:35 -0800 (PST)
To: Snob Art Genre <ben@narcissus.ml.org>
cc: "K.J.Koster" <kjk1@ukc.ac.uk>, hackers@FreeBSD.org
Subject: Re: A simple way to crash your system. 
In-reply-to: Your message of "Mon, 25 Nov 1996 13:14:17 PST."
             <Pine.BSF.3.91.961125131249.16405B-100000@narcissus.ml.org> 
Date: Mon, 25 Nov 1996 17:03:35 -0800
Message-ID: <8484.848970215@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
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.
> 
> There is no documentation of the fact that it's that screwed up, which is
> something that whoever's responsible for documenting these things might
> want to look into. 

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.

Any strong votes to the contrary?  I don't think there's anything
about the current msdosfs we want to keep anyway.

					Jordan