9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] mount 9P on Linux and FreeBSD via FUSE
Date: Wed, 26 Jul 2006 22:39:11 -0700	[thread overview]
Message-ID: <ee9e417a0607262239v77d8642fg35f57442f26a8b31@mail.gmail.com> (raw)

Various changes to p9p over the weekend;
see http://swtch.com/usr/local/plan9/CHANGES.

The changes center around a new program called 9pfuse
(inspired by Christoph Lohmann's program of the same name)
that mounts 9P servers on Linux and FreeBSD via FUSE.
9pfuse uses the raw FUSE message format instead of using
the high-level library interface, which actually hides some
details important to a faithful translation.

The net result is that I can do:

	x40=; 9 mount `namespace`/acme /mnt/acme
	x40=; ls /mnt/acme
	309  355  356  acme  cons  consctl  draw  editout  index  label  new
	x40=; cat /mnt/acme/356/body
	Hello, FUSE!
	x40=; unmount /mnt/acme
	x40=;

Thanks to Lou Kamenov for working through some FreeBSD
bugs.  If you want to use 9pfuse on FreeBSD you'll need the
very latest FUSE implementation (this morning's), which
fixes some protocol errors on the part of the kernel module.

And thanks to Christoph Lohmann for writing the other 9pfuse.

Russ


             reply	other threads:[~2006-07-27  5:39 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27  5:39 Russ Cox [this message]
2006-07-27  6:03 ` csant
2006-07-27  6:09   ` andrey mirtchovski
2006-07-27  6:21     ` csant
2006-07-27 11:58       ` Anthony Sorace
2006-07-27 14:40         ` Russ Cox
2006-07-27 16:24           ` andrey mirtchovski
2006-07-27 16:41             ` csant
2006-07-27 16:43               ` andrey mirtchovski
2006-07-27 16:47                 ` csant
2006-07-27 16:50                   ` andrey mirtchovski
2006-07-27 17:00                     ` csant
2006-07-27 19:41                     ` Charles Forsyth
2006-07-27 22:13                       ` andrey mirtchovski
2006-07-27 22:20                         ` Skip Tavakkolian
2006-07-27 22:36                         ` Russ Cox
2006-07-27 22:56                       ` geoff
2006-07-28  1:29                         ` Russ Cox
2006-07-28  2:12                         ` erik quanstrom
2006-07-28  2:31                           ` Gorka guardiola
2006-07-28  6:17                           ` csant
2006-07-28  6:38                             ` David Leimbach
2006-07-28 10:48                               ` erik quanstrom
2006-07-28 13:54                                 ` David Leimbach
2006-07-28 15:01                               ` Ronald G Minnich
2006-07-28 12:39                             ` Eric Van Hensbergen
2006-07-28 13:56                               ` David Leimbach
2006-07-28 14:22                                 ` erik quanstrom
2006-07-28 14:57                             ` Ronald G Minnich
2006-07-28  9:21                     ` Scott Schwartz
2006-07-28 15:08                       ` Ronald G Minnich
2006-07-28 15:44                         ` Eric Van Hensbergen
2006-07-28 20:41                         ` Scott Schwartz

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=ee9e417a0607262239v77d8642fg35f57442f26a8b31@mail.gmail.com \
    --to=rsc@swtch.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).