From owner-freebsd-current Thu Oct 30 07:29:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA15094 for current-outgoing; Thu, 30 Oct 1997 07:29:33 -0800 (PST) (envelope-from owner-freebsd-current) Received: from veda.is (adam@veda.is [193.4.230.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA15085 for ; Thu, 30 Oct 1997 07:29:23 -0800 (PST) (envelope-from adam@veda.is) Received: (from adam@localhost) by veda.is (8.8.7/8.8.5) id PAA07158 for freebsd-current@freebsd.org; Thu, 30 Oct 1997 15:29:04 GMT From: Adam David Message-Id: <199710301529.PAA07158@veda.is> Subject: MFS ? To: freebsd-current@freebsd.org Date: Thu, 30 Oct 1997 15:29:03 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I noticed a commit involving MFS the other day, but it didn't say anything about this fixing MFS so I guess it's still in the no-go zone? What would happen if I tried to use MFS with it broken? Would it just not run, or would it grow legs and stomp all over the place? -- Adam David