From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <140e7ec30810050835jdf02297g4a89eadf103826f0@mail.gmail.com>
Date: Sun,  5 Oct 2008 23:35:24 +0800
From: sqweek <sqweek@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
In-Reply-To: <1223061499.22031.9.camel@goose.sun.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <1223061499.22031.9.camel@goose.sun.com>
Subject: Re: [9fans] mounting stdin using 9pfuse
Topicbox-Message-UUID: 17321344-ead4-11e9-9d60-3106f5b1d025

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