From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <140e7ec30907140034j5a206e44oc36cc19fa805d63c@mail.gmail.com>
References: <Pine.BSI.4.64.0907110843190.5249@malasada.lava.net>
	<0F3972F5-D44B-4231-97FA-C6CE871B032B@gmail.com>
	<Pine.BSI.4.64.0907110901260.5249@malasada.lava.net>
	<140e7ec30907130124g1a0e4c90m6d83a08516d95463@mail.gmail.com>
	<f158dc670907130808g6ecfdf44ncf3f4b3b82c1b611@mail.gmail.com>
	<140e7ec30907140034j5a206e44oc36cc19fa805d63c@mail.gmail.com>
Date: Tue, 14 Jul 2009 08:37:48 -0600
Message-ID: <f158dc670907140737r43243148pe038aba4e04c820b@mail.gmail.com>
From: Latchesar Ionkov <lucho@ionkov.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] v9fs question
Topicbox-Message-UUID: 1fd2a3f0-ead5-11e9-9d60-3106f5b1d025

On Tue, Jul 14, 2009 at 1:34 AM, sqweek<sqweek@gmail.com> wrote:
> =A0Can't help you there - I'm not sure it makes sense to try and put
> factotum's functionality in the linux kernel... Is there some problem
> with the private namespace/individual user mount approach?
> -sqweek

I don't want to put the authentication in the kernel, but somehow to
allow user space programs to create and manipulate authentication
fids. One option would be to expose the afids in /proc or /sys, but
then it is hard to figure out what mount they belong to. Another
option is for every mount, v9fs serves mntpt/.afids directory at the
top of the mountpoint.

Or, as Ron suggested, just forget about multiple users and make it
work for a single one.

Thanks,
    Lucho