9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ronald G Minnich <rminnich@lanl.gov>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] mount 9P on Linux and FreeBSD via FUSE
Date: Fri, 28 Jul 2006 09:08:17 -0600	[thread overview]
Message-ID: <44CA2861.5060104@lanl.gov> (raw)
In-Reply-To: <20060728092155.GB20048@bio.cse.psu.edu>

Scott Schwartz wrote:

> Is there enough 9p support in linux 2.6 to do that without fuse?

now you're depressing me. Yes, you can do 9p in linux 2.6 without fuse.
You just do a mount. I set a lot of mine up in /etc/fstab.

Or do you mean user mounts? Maybe I missed something.

> Can someone who understands both compare this to v9fs?

Fuse is cute, it works, it's fine for the local case. It seems to be
pretty solid. A very nice point solution, completely useless for what we
do here at LANL. It seems to be easier for people to figure out than 9p
servers. Another issue is that to date the 9p server libraries we had
were mostly p9p-based, and Linux people prefer not to use p9p libraries
to write software, I'm finding. Nothing wrong with p9p libraries, people
just don't want to deal with them. Lucho has developed native Unix
libraries which are pretty nice, and we're moving our software over to
those.

thanks


ron


  reply	other threads:[~2006-07-28 15:08 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27  5:39 Russ Cox
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 [this message]
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=44CA2861.5060104@lanl.gov \
    --to=rminnich@lanl.gov \
    --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).