From owner-freebsd-hackers Mon Jun 24 16: 6:28 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 0334B37B400 for ; Mon, 24 Jun 2002 16:06:23 -0700 (PDT) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.3/8.12.3) with ESMTP id g5ON6Nl1000624; Mon, 24 Jun 2002 16:06:23 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.3/8.12.3/Submit) id g5OMXHl8000378; Mon, 24 Jun 2002 15:33:17 -0700 (PDT) (envelope-from dillon) Date: Mon, 24 Jun 2002 15:33:17 -0700 (PDT) From: Matthew Dillon Message-Id: <200206242233.g5OMXHl8000378@apollo.backplane.com> To: Terry Lambert Cc: Harry Newton , freebsd-hackers@FreeBSD.ORG Subject: Re: status of portalfs References: <86adpkih9j.fsf@basilisk.locus> <3D179464.4538513D@mindspring.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Actually Terry is wrong here :-) Sorry Terry. The portal filesystem is not really a filesystem. All it can do is intercept open()s and return descriptors. It isn't like NULLFS. The portal filesystem does not do any layering at all. open() does not return a portalfs descriptor. What portalfs does is connect to a unix domain socket (aka a userland process) and then it expects a control message to sent to it with a descriptor (like to a normal file or a TCP socket or whatever). It then returns the descriptor directly. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message