9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Gorka guardiola <paurea@gmail.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] afid and fd, mapping from user space
Date: Sun,  3 Jul 2005 23:48:21 +0200	[thread overview]
Message-ID: <599f06db0507031448636afcbd@mail.gmail.com> (raw)
In-Reply-To: <ee9e417a050702164663bfa391@mail.gmail.com>

I was just thinking about the more general problem of converting a fid
to a fd and/or backwards
so I could do read and write and let the kernel do the 9P chat for me.
Maybe other programs could benefit from it. The idea comes from the
fact that fauth does the work, but there is no way to recover the fid
after to use it in the attach, which is frustrating.

I am doing the proxy by hand now (still working on it) anyway.

On 7/3/05, Russ Cox <russcox@gmail.com> wrote:
> The right solution is to proxy between factotum and the fids manually.
> Auth_proxy was intended to be simple, not a black box.
>


  reply	other threads:[~2005-07-03 21:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-01 22:20 Gorka guardiola
2005-07-02 23:46 ` Russ Cox
2005-07-03 21:48   ` Gorka guardiola [this message]
2005-07-07  2:33 ` rog
2005-07-07 10:38   ` Russ Cox

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=599f06db0507031448636afcbd@mail.gmail.com \
    --to=paurea@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).