From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <6cdb4535f5bb66418e0ecca111855443@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] an idea
From: rog@vitanuova.com
In-Reply-To: <9e4e21fc6d55eeda301f48ae41fd6304@terzarima.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Mon, 26 Apr 2004 17:57:59 +0100
Topicbox-Message-UUID: 6e865daa-eacd-11e9-9e20-41e7f4b1d025

> the thing that applies the capability must be in the kernel to
> affect kernel-related data, so i'm not sure it's very different in
> practice from a driver doing the same.

you need one system call to allow a process to translate from local
capability (fd) to external capability (a string).  that can't be
implemented in the namespace itself because the namespace might not be
implemented locally (for instance things can still work correctly if
iostats is mediating the entire namespace).

the translation the other way (from capability to fd) can, and should,
be implemented by a kernel device.