From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nir Tzachar Subject: Re: [PATCH] private mounts Date: Tue, 10 May 2005 21:28:25 +0300 (IDT) Message-ID: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: Received: from indigo.cs.bgu.ac.il ([132.72.42.23]:35266 "EHLO indigo.cs.bgu.ac.il") by vger.kernel.org with ESMTP id S261729AbVEJS0l (ORCPT ); Tue, 10 May 2005 14:26:41 -0400 Received: from lvs-rs1 (lvs-rs1 [132.72.41.60]) by indigo.cs.bgu.ac.il (8.13.1/8.13.1) with ESMTP id j4AISOvB014723 for ; Tue, 10 May 2005 21:28:26 +0300 (IDT) To: linux-fsdevel@vger.kernel.org Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org hello. please shout if im missing something, but i think there can be a simple solution (which involves quite a bit of coding....). Why not implement FUSE as a user space applications --> not involving any kernel code at all. what i have in mind is replacing the user space daemon (which FUSE currently utilizes to speak with the kernel) with a different daemon. i suggest using a user space nfs daemon, which can than be mounted on the local (or on a remote) machine as a regular nfs exported fs. this solution seems to solve the permissions problems and simplifies things a bit, since no kernel code is needed (apart from allowing user mounts). however, implementing this is quit involved, and im sure several hurdles must be passed along the way. regardless, i think the benefits can outweigh such drawbacks..... -- ======================================================================== nir.