From owner-freebsd-fs Mon Jun 22 20:54:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18092 for freebsd-fs-outgoing; Mon, 22 Jun 1998 20:54:32 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18057; Mon, 22 Jun 1998 20:54:22 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id UAA24405; Mon, 22 Jun 1998 20:54:14 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp02.primenet.com, id smtpd024319; Mon Jun 22 20:54:08 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id UAA06135; Mon, 22 Jun 1998 20:54:01 -0700 (MST) From: Terry Lambert Message-Id: <199806230354.UAA06135@usr09.primenet.com> Subject: Re: Stackable filesystems and SunOS 4.1.1 To: michaelh@cet.co.jp (Michael Hancock) Date: Tue, 23 Jun 1998 03:54:00 +0000 (GMT) Cc: tlambert@primenet.com, Matthew.Alton@anheuser-busch.com, FreeBSD-fs@FreeBSD.ORG, Hackers@FreeBSD.ORG, Scott.Smallie@anheuser-busch.com In-Reply-To: from "Michael Hancock" at Jun 23, 98 10:30:09 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > You're missing the point. The original proposal was for a non-stacked > userland fs development environment where everything was to implemented > from scratch so that it could be made as portable as possible. > > Is this ... > > 1) easy > 2) less easy > > ... compared to the approach you used at your previous employer. ;-) Do I get all the VOP patches and private vnode management patches, and my own advisory locking patches (it's easy to proxy a veto interface, hard to proxy a lockmgr() call) and my namei() patches (the origin of ISUNICODE in namei.h) and nameifree() as a base to work with? If so, then it's about the same. Much of the work in Windows 95 was mapping the IFSMgr calls to VOP's, on the top end, and emulating about 70 kernel interfaces (down from the 126 FreeBSD's FFS requires) in Windows 95 Ring 0. Much of the complexity there was in the timer outcall for the syncd, since Windows 95 "semaphores" are unfortunately thread reentrant. Most of the remaining 70 interfaces have corrolaries in FreeBSD user space, being that FreeBSD is FreeBSD derived. 8-). Do I have to proxy the grotesqueries that are the cookie interface, instead of spliting the directory lookup, directory entry copyout, the nameifree() asymmetry, etc.? Then it's about twice the work. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message