9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] mount 9P on Linux and FreeBSD via FUSE
Date: Thu, 27 Jul 2006 21:12:56 -0500	[thread overview]
Message-ID: <a78a8ae67e80c425fdf188d55e5981f7@quanstro.net> (raw)
In-Reply-To: <1368134f2e2a5a7ae0f41603e8c7ce2e@collyer.net>

i use this in my /etc/fstab

/tmp/ns.quanstro.:0/acme	/home/quanstro/9/acme	9P	uid=1000,user,name=quanstro,proto=unix,noauto	0 0
/tmp/ns.quanstro.:0/upasfs	/home/quanstro/9/upasfs	9P	uid=1000,user,name=quanstro,proto=unix,noauto	0 0
/tmp/ns.quanstro.:0/sources	/home/quanstro/9/sources	9P	uid=1000,user,name=quanstro,proto=unix,noauto	0 0
/tmp/ns.quanstro.:0/tapefs	/home/quanstro/9/tapefs	9P	uid=1000,user,name=quanstro,proto=unix,noauto	0 0
/tmp/ns.quanstro.:0/dns	/home/quanstro/9/dns	9P	uid=1000,user,name=quanstro,proto=unix,noauto	0 0

this allows me (without becoming root or having v9fs) to
	; mount $home/9/acme
assuming that acme is running and my current namespace is the default.

- erik

On Thu Jul 27 17:58:11 CDT 2006, geoff@collyer.net wrote:
> I had 9P mounting working but the v9fs (9P) module has vanished from
> my Linux machine.  As root, I invoked the equivalent in C of
>
> 	mount -t 9P -o proto=fd,name=$LOGNAME,rfdno=%d,wfdno=%d '' /n/remote
>
> where %d is the file descriptor to communicate with the 9P server.
> The more common usage is
>
> 	mount -t 9P -o name=geoff 10.240.55.178 /n/remote


  parent reply	other threads:[~2006-07-28  2:12 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 [this message]
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=a78a8ae67e80c425fdf188d55e5981f7@quanstro.net \
    --to=quanstro@quanstro.net \
    --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).