9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Roman V. Shaposhnik" <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] mounting stdin using 9pfuse
Date: Mon,  6 Oct 2008 20:47:41 -0700	[thread overview]
Message-ID: <1223351261.19902.22.camel@goose.sun.com> (raw)
In-Reply-To: <ee9e417a0810060931w3a5b143ax2f9244344927b2a6@mail.gmail.com>

On Mon, 2008-10-06 at 09:31 -0700, Russ Cox wrote:
> > it appears that I'm missing something fundamental in how
> > 9pfuse (the one written by Russ) works when it is given
> > "-" as an address. The source looks like it should be
> > simply using stdin for R/W instead of dialing out the
> > connection first, but it doesn't really seem to work.
> > Here's the simplest way of reproducing what I'm
> > seeing:
>
> I don't know why your example doesn't work, but ramfs
> simply may not work with 9pfuse.

Any particular reason for that? I'm asking simply because
ramfs appears to be quite broken on my system. In fact,
I can't make it work at all. Has it bitrotted?

> I would try doing something
> a little more complicated, like dial tcp!sources.cs.bell-labs.com!9fs
> and then run 9pfuse - with that on standard input.

That, actually, seems to work fine. Although I'm about
to give it more stress testing. Here's a question thought:
by default 9pserve only listens on an AF_UNIX socket what
would be the best way to connect it to the AF_INET one?

Thanks,
Roman.




  reply	other threads:[~2008-10-07  3:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-03 19:18 Roman V. Shaposhnik
2008-10-05 15:35 ` sqweek
2008-10-06  3:46   ` Roman V. Shaposhnik
2008-10-06  4:56     ` sqweek
2008-10-06 16:31 ` Russ Cox
2008-10-07  3:47   ` Roman V. Shaposhnik [this message]
2008-10-07  7:48     ` sqweek

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=1223351261.19902.22.camel@goose.sun.com \
    --to=rvs@sun.com \
    --cc=9fans@9fans.net \
    /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).