From owner-freebsd-current  Sun Oct 19 12:36:22 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id MAA27891
          for current-outgoing; Sun, 19 Oct 1997 12:36:22 -0700 (PDT)
          (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 MAA27880;
          Sun, 19 Oct 1997 12:36:10 -0700 (PDT)
          (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 VAA00522;
	Sun, 19 Oct 1997 21:35:14 +0200 (CEST)
To: dyson@FreeBSD.ORG
cc: grog@lemis.com (Greg Lehey), smp@csn.net, current@FreeBSD.ORG
Subject: Re: usable current SNAP 
In-reply-to: Your message of "Sat, 18 Oct 1997 21:47:24 CDT."
             <199710190247.VAA01886@dyson.iquest.net> 
Date: Sun, 19 Oct 1997 21:35:14 +0200
Message-ID: <520.877289714@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 <199710190247.VAA01886@dyson.iquest.net>, "John S. Dyson" writes:

>MFS doesn't work in -current, and I am working on it now.  I have been
>happiest with about Oct10 or so.

I'll look at this rsn.  What MFS does to protect it's "parent" vnode
is pretty disgusting actually, and maybe not a good idea at all,

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