Date: Mon, 25 Nov 1996 20:48:57 -0700 (MST) From: Nate Williams <nate@mt.sri.com> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: Nate Williams <nate@mt.sri.com>, hackers@freebsd.org Subject: Re: A simple way to crash your system. Message-ID: <199611260348.UAA02926@rocky.mt.sri.com> In-Reply-To: <8867.848975625@time.cdrom.com> References: <199611260208.TAA02586@rocky.mt.sri.com> <8867.848975625@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[ Removing 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. > > I understand this, but you also have to realize that many people don't > understand the fragile china approach (and with justification - how > *would* one generally know?) and it's a real setback to have your UFS > filesystems blown away too. :-) Agreed, but removing it wholesale isn't a very good approach either, since it also means that someone who might have the gumption to fix it won't have a starting point. We ship lots of broken FS implementations now, so I think we should continue to ship a broken/hobbling MSDOSFS. Simply not advertising it is one solution, or have mount_msdos print out something 'Danger Will Robinson, danger' might be a solution. :) :) Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611260348.UAA02926>