9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Re: [9fans] mount 9P on Linux and FreeBSD via FUSE
Date: Fri, 28 Jul 2006 06:56:45 -0700	[thread overview]
Message-ID: <3e1162e60607280656h3ae3736brdc66a08d5ec2253d@mail.gmail.com> (raw)
In-Reply-To: <a4e6962a0607280539k505f75ai138544622f0bdec9@mail.gmail.com>

On 7/28/06, Eric Van Hensbergen <ericvh@gmail.com> wrote:
> On 7/28/06, csant <csant@csant.info> wrote:
> > > this allows me (without becoming root or having v9fs) to
> > >       ; mount $home/9/acme
> >
> > But you'd have the 9p module, obviously. It's such a nonsene that the
> > linux kernel doesn't allow mounting for non-privileged users
> > out-of-the-box, IMO. I like filesystems in userspace.
> >
>
> This was discussed a bit at OLS -  there have been folks working
> towards it for a bit, but I think we'll finally see it within the next
> year.

I wonder how dragonflyBSD is coming along with their VFS "messaging"
stuff.  They want to make it easy to do SSI clusters (single system
image).  It sounds like FUSE would be completely redundant on this
platform, and one could implement 9p translation trivially.

I once asked if Matt had even looked at plan 9's way of making things
plug into the filesystem namespace via 9p and I actually don't
remember what his response was but he seemed that he really wanted to
do it his way :-)

Dave

>
>        -eric
>


  reply	other threads:[~2006-07-28 13:56 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 [this message]
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=3e1162e60607280656h3ae3736brdc66a08d5ec2253d@mail.gmail.com \
    --to=leimy2k@gmail.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).