From: "Roman V. Shaposhnik" <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Cc: lucio@proxima.alt.za
Subject: Re: [9fans] Why do we need syspipe() ?
Date: Thu, 8 Jan 2009 15:36:04 -0800 [thread overview]
Message-ID: <1231457764.6916.79.camel@goose.sun.com> (raw)
In-Reply-To: <df49a7370901050300k2a124f34jf4ff08ca8e22f837@mail.gmail.com>
On Mon, 2009-01-05 at 11:00 +0000, roger peppe wrote:
> i've sometimes thought that the trick used by #d etc could
> be made more transparent by providing a genuine capability
> service for fds, in the form of a system call, for instance
>
> getfdcap(int fd, char *buf, int len)
>
> then instead of just writing the fd itself, you'd write
> the capability - thus the write can bridge several
> namespaces, as long as it ends up in the same kernel,
> which can then utilise the capability.
>
> the fact that this also provides the possibility of implementing
> sendfd might or might not be an advantage.
In light of the recent discussion, I now see how providing this
basic capability could be a very useful building block for the
rest of the system.
Not in a sense, that it'll be plugging a particular gaping hole,
but rather that thrown into the mix, it might help foster better
ideas/implementations.
Thanks,
Roman.
next prev parent reply other threads:[~2009-01-08 23:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 5:04 Roman V. Shaposhnik
2009-01-04 6:56 ` Russ Cox
2009-01-05 4:39 ` Roman V. Shaposhnik
2009-01-05 6:20 ` Russ Cox
2009-01-05 7:28 ` lucio
2009-01-05 11:00 ` roger peppe
2009-01-08 23:36 ` Roman V. Shaposhnik [this message]
2009-01-06 17:40 ` Nathaniel W Filardo
2009-01-06 20:37 ` Charles Forsyth
2009-01-06 23:13 ` Roman V. Shaposhnik
2009-01-06 23:15 ` erik quanstrom
2009-01-08 23:45 ` Roman V. Shaposhnik
2009-01-08 23:48 ` erik quanstrom
2009-01-09 2:05 ` Roman V. Shaposhnik
2009-01-09 12:54 ` roger peppe
2009-01-07 3:48 ` lucio
2009-01-07 7:00 ` Roman Shaposhnik
2009-01-07 9:31 ` Charles Forsyth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1231457764.6916.79.camel@goose.sun.com \
--to=rvs@sun.com \
--cc=9fans@9fans.net \
--cc=lucio@proxima.alt.za \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).