From owner-freebsd-hackers Mon Nov 25 18:36:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA29531 for hackers-outgoing; Mon, 25 Nov 1996 18:36:04 -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 SAA29449 for ; Mon, 25 Nov 1996 18:34:58 -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 SAA08869; Mon, 25 Nov 1996 18:33:46 -0800 (PST) To: Nate Williams cc: Snob Art Genre , "K.J.Koster" , hackers@freebsd.org Subject: Re: A simple way to crash your system. In-reply-to: Your message of "Mon, 25 Nov 1996 19:08:10 MST." <199611260208.TAA02586@rocky.mt.sri.com> Date: Mon, 25 Nov 1996 18:33:45 -0800 Message-ID: <8867.848975625@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 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. :-) I'd welcome some compromise solutions, otherwise I think it's simply too dangerous to advertise, explicitly or implicitly, as a feature. Jordan