From owner-freebsd-hackers Thu Jul 22 9:53:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rebel.net.au (rebel.rebel.net.au [203.20.69.66]) by hub.freebsd.org (Postfix) with ESMTP id 9012114C20 for ; Thu, 22 Jul 1999 09:53:51 -0700 (PDT) (envelope-from kkenn@rebel.net.au) Received: from 203.20.69.80 (dialup-10.rebel.net.au [203.20.69.80]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id CAA27079 for ; Fri, 23 Jul 1999 02:23:35 +0930 Received: (qmail 10413 invoked from network); 22 Jul 1999 16:53:41 -0000 Received: from localhost (kkenn@127.0.0.1) by localhost with SMTP; 22 Jul 1999 16:53:41 -0000 Date: Fri, 23 Jul 1999 02:23:39 +0930 (CST) From: Kris Kennaway Reply-To: kkenn@rebel.net.au To: "Ronald G. Minnich" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Filesystem question... In-Reply-To: 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 Thu, 22 Jul 1999, Ronald G. Minnich wrote: > what if you're not root, and you want to add your own file system to your > file system name space? It seems a lot of these systems assume root > access, which seems unrealistic to me. Well, if you're running it as a kernel module then obviously you need root permissions to load it. If it's running as a userland process, then there's no reason why you can't run it as a user. mount presumably wouldn't care as long as you had access rights to the underlying objects (mountpoint + stacking layer process). Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message