9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Eric Van Hensbergen" <ericvh@gmail.com>
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 10:44:55 -0500	[thread overview]
Message-ID: <a4e6962a0607280844m72be5d4eu217c903a9a268d25@mail.gmail.com> (raw)
In-Reply-To: <44CA2861.5060104@lanl.gov>

On 7/28/06, Ronald G Minnich <rminnich@lanl.gov> wrote:
> 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.
>

User mounts (w/either FUSE or 9p) can be "tricked out" with a set-uid
mount helper (9p's would be called mount.9P I think).  Such a helper
is also needed in 9p to do DNS resolution (NFS name resolution is the
only special-case in mount).  I believe Lucho had a 9p helper that
took care of DNS resolution, could be made setuid and maybe even tried
to handle auth.
Its in the app directory on v9fs' sourceforge CVS. The discussion of
OLS was about how to remove the need for having a set-uid helper.

     -eric


  reply	other threads:[~2006-07-28 15:44 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
2006-07-28 15:44                         ` Eric Van Hensbergen [this message]
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=a4e6962a0607280844m72be5d4eu217c903a9a268d25@mail.gmail.com \
    --to=ericvh@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).