9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: fernanbolando@mailc.net, 9fans@cse.psu.edu
Subject: Re: [9fans] v9fs and Russ tra
Date: Sat,  1 Apr 2006 16:14:04 -0500	[thread overview]
Message-ID: <6bd9d8ab7be366ce990e3d03e9eefeb9@swtch.com> (raw)
In-Reply-To: <1d5d51400604011135w53273453vd493784c2b61146d@mail.gmail.com>

> running listen tcp!*!564 and il!*!17008 did the trick with the
> fossil not listening. Now I am getting "permission denied" so I guess
> this is is what you meant by auth problems.

If you have p9p installed, that's enough to mount with v9fs.
You can use srv -a to get a preauthenticated Unix socket
and then just mount it like any other Unix socket.
For example, if I use:

	srv -a sources.cs.bell-labs.com sources
	sudo mount -t 9P -o user=$USER,uid=`id -u`,gid=`id -g`,proto=unix \
		`namespace`/sources /n/sources

then I can read and write files on sources.

> [question about tra and plan 9]

Tra doesn't run on Plan 9 just now.  It is based on p9p,
so it shouldn't be hard to get up and running.
I reworked most of it recently so it is unproven.
I'd only use it with regular backups for now.

Russ



  reply	other threads:[~2006-04-01 21:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-01  5:38 Fernan Bolando
2006-04-01 17:26 ` "Nils O. Selåsdal"
2006-04-01 18:44   ` Eric Van Hensbergen
2006-04-01 19:35     ` Fernan Bolando
2006-04-01 21:14       ` Russ Cox [this message]
2006-04-03  3:57         ` Jeff Sickel
2006-04-03 18:46           ` Ronald G Minnich
2006-04-03 19:10             ` Bakul Shah
2006-04-03 19:34               ` Ronald G Minnich
2006-04-04 17:31                 ` Tim Wiess
2006-04-04 17:44                   ` Tim Wiess
2006-04-05  2:16                     ` Ronald G Minnich
2006-04-05 16:20                       ` Tim Wiess
2006-04-02  2:46 ` Russ Cox
2006-04-02  3:16 erik quanstrom
2006-04-02  3:40 ` Russ Cox
2006-04-04  4:19 YAMANASHI Takeshi

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=6bd9d8ab7be366ce990e3d03e9eefeb9@swtch.com \
    --to=rsc@swtch.com \
    --cc=9fans@cse.psu.edu \
    --cc=fernanbolando@mailc.net \
    /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).