From owner-freebsd-current  Thu Oct 30 08:31:03 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id IAA18267
          for current-outgoing; Thu, 30 Oct 1997 08:31:03 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA18244
          for <freebsd-current@FreeBSD.ORG>; Thu, 30 Oct 1997 08:30:59 -0800 (PST)
          (envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1])
	by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id RAA00316;
	Thu, 30 Oct 1997 17:20:33 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: Adam David <adam@veda.is>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: MFS ? 
In-reply-to: Your message of "Thu, 30 Oct 1997 15:29:03 GMT."
             <199710301529.PAA07158@veda.is> 
Date: Thu, 30 Oct 1997 17:20:32 +0100
Message-ID: <314.878228432@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

In message <199710301529.PAA07158@veda.is>, Adam David writes:
>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?

It was to remove a non-fatal warning.
>
>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?

Have I missed a report on it being broken ?

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."