From owner-freebsd-hackers Mon Nov 25 18:08:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA27641 for hackers-outgoing; Mon, 25 Nov 1996 18:08:57 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA27613 for ; Mon, 25 Nov 1996 18:08:39 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id TAA02586; Mon, 25 Nov 1996 19:08:10 -0700 (MST) Date: Mon, 25 Nov 1996 19:08:10 -0700 (MST) Message-Id: <199611260208.TAA02586@rocky.mt.sri.com> From: Nate Williams To: "Jordan K. Hubbard" Cc: Snob Art Genre , "K.J.Koster" , hackers@freebsd.org Subject: Re: A simple way to crash your system. In-Reply-To: <8484.848970215@time.cdrom.com> References: <8484.848970215@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. > > 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. Nate