9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: sqweek <sqweek@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] mounting stdin using 9pfuse
Date: Sun,  5 Oct 2008 23:35:24 +0800	[thread overview]
Message-ID: <140e7ec30810050835jdf02297g4a89eadf103826f0@mail.gmail.com> (raw)
In-Reply-To: <1223061499.22031.9.camel@goose.sun.com>

On Sat, Oct 4, 2008 at 3:18 AM, Roman V. Shaposhnik <rvs@sun.com> 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.

 Seems to work here on linux after:
 #include <error.h>
 #include <errno.h>
+#include <unistd.h>

 void socket012(int fd)
 {
   int i;
-  for (i=0; i<3; i++) {
+ for (i=0; i<2; i++) {
        close(i);
        dup2(fd, i);

    if (fork()) {
        socket012(fd[0]);
-       execlp("9pfuse", "9pfuse", "-", "/tmp/fuse", (char*)0);
+       execlp("9pfuse", "9pfuse", "-D", "-", "/tmp/fuse", (char*)0);
    } else {
        socket012(fd[1]);

 ls -l caused a failed assertion in ramfs, but it was going. Can't
justify why the diff works, but before adding -D and changing 3 -> 2 I
didn't have any success. Would love to look into it further but in the
interest of not destroying my work schedule this week I'm going to get
some damn sleep. Good luck.
-sqweek



  reply	other threads:[~2008-10-05 15:35 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 [this message]
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
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=140e7ec30810050835jdf02297g4a89eadf103826f0@mail.gmail.com \
    --to=sqweek@gmail.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).