9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Fuse to 9p bridge?
Date: Fri, 12 Jan 2007 11:39:42 -0800	[thread overview]
Message-ID: <61e719f29af0f5ecbbd518dd81cee7df@9netics.com> (raw)
In-Reply-To: <509071940701121106k25e8b260xe27a39c83a4ae4bd@mail.gmail.com>

> there is indeed: see $PLAN9/src/cmd/9pfuse. i think this just made my day.

make sure to use the Genuine Russ version of 9pfuse (as noted above).
there is another package by the same name that is a toy.



  parent reply	other threads:[~2007-01-12 19:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12 18:49 Paul Lalonde
2007-01-12 19:02 ` David Leimbach
2007-01-12 19:06 ` Anthony Sorace
2007-01-12 19:20   ` David Leimbach
2007-01-12 19:39   ` Skip Tavakkolian [this message]
2007-01-12 20:16     ` Anthony Sorace
2007-01-18  3:00       ` Jeff Sickel
2007-01-12 19:33 ` Steve Simon
2007-01-12 19:38   ` Paul Lalonde
2007-01-12 20:09     ` Skip Tavakkolian

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=61e719f29af0f5ecbbd518dd81cee7df@9netics.com \
    --to=9nut@9netics.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).