From owner-freebsd-hackers Fri May 7 10:42:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 8F99715247 for ; Fri, 7 May 1999 10:42:29 -0700 (PDT) (envelope-from rminnich@acl.lanl.gov) Received: from localhost (rminnich@localhost) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id LAA507199 for ; Fri, 7 May 1999 11:42:29 -0600 (MDT) Date: Fri, 7 May 1999 11:42:29 -0600 From: "Ronald G. Minnich" To: hackers@FreeBSD.ORG Subject: Re: memory-based VFS In-Reply-To: <199905071646.JAA45627@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 May 1999, Matthew Dillon wrote: > Not to detract from the cool things people have been writing, but > in FreeBSD-current, it is possible to directly swap-back the VN device > and mount a softupdates-enabled filesystem over it. You effectively get Quite cool. This still doesn't do what v9fs does, though. v9fs is a simple VFS (which aspiring VFS writers can use as a tutorial) which is intended as the starting point for private name spaces for freebsd. As such, we need to grab control at the vnop level. We looked at -current to see if there was a suitable candidate, and found none: hence v9fs. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message