[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: firmlinks and chroots
From: |
olafBuddenhagen |
Subject: |
Re: firmlinks and chroots |
Date: |
Tue, 18 Sep 2007 11:43:10 +0200 |
User-agent: |
Mutt/1.5.16 (2007-06-11) |
Hi,
On Fri, Sep 14, 2007 at 01:26:55AM +0200, Marcus Brinkmann wrote:
> * Passive translators can be stored in inodes, when they are
> encountered the filesystem propagates the request to install an active
> translator to the translator server of that user. (This matches most
> closely what is happening now, just that the active translator is not
> started by the filesystem but by the user owning the node).
I actually considered this variant right after reading your original
proposal. Seems quite promising to me :-)
> * Passive translators can be stored in inodes. The C library can see
> these settings, and either start an active translator itself (this
> works best with private namespaces or private parts of a global
> namespace---it's basically what's going on magically with /dev/fd/N,
> just that there is no extra process needed), or contact the
> "translator server" to let it start an active translator. (Extended
> attributes could hint at what should happen). This does only work
> easily for nodes owned by the same user.
>
> If the node is owned by another user, that other user's translator
> server needs to be contacted instead.
This is a more fundamental change. I have no opinion on it yet...
-antrik-