From: sqweek <sqweek@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] 9P on linux
Date: Tue, 15 Jan 2008 03:53:06 +0900 [thread overview]
Message-ID: <140e7ec30801141053x6725cc2bwb75f80d8384c04db@mail.gmail.com> (raw)
In-Reply-To: <c5cb8491-8d0b-4d32-b989-c0f551fbf885@n20g2000hsh.googlegroups.com>
On Jan 14, 2008 6:56 PM, <jhutchence@gmail.com> wrote:
> I am having trouble getting 9P working on my linux box. Firstly u9fs:
> I have followed the directions on http://www.t3x.org/bits/plan9_on_u9fs.html
> and put put this line in /etc/inetd.conf
>
> u9fs stream tcp nowait root /root/bin/u9fs u9fs -Dz -a
> p9any /scratch/p9root
>
> the only client I have even been able to run is this one:
> http://www.lava.net/~newsham/plan9/
I'd recommend running with p9p[1] for testing. Here's my setup (wren
is the server, nightingale the client):
wren:/etc/inetd.conf:31:564 stream tcp nowait root
/usr/local/bin/u9fs u9fs -a p9any
nightingale$ 9 factotum
nightingale$ srv -a wren
Adding key for proto=p9sk1 authdom=sqweek.dnsdojo.org ...
User [sqweek]:
Password: *********
nightingale$ 9p ls wren/home
d-rwxr-xr-x M 0 sqweek users 1024 Jan 10 16:43 sqweek
Brief explanation - "9 factotum" starts up the password manager (for
lack of a better term), and "srv -a wren" starts an authenticated
connection to my server (via tcp on port 564, since I didn't specify).
Both of these commands place a socket in my 'namespace' directory,
/tmp/ns.sqweek.:0, for further communication. srv then communicates
with factotum to achieve authentication, and finally the 9p command
uses the "wren" socket that srv created. I also mount it with
9p2000.ko using "mount -t 9p -o proto=unix,noextend
/tmp/ns.sqweek.:0/wren /home/sqweek/n/wren".
[1] http://swtch.com/plan9port/
prev parent reply other threads:[~2008-01-14 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 9:56 jhutchence
2008-01-14 10:13 ` Rodolfo kix García
2008-01-14 13:38 ` Eric Van Hensbergen
2008-01-14 18:53 ` sqweek [this message]
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=140e7ec30801141053x6725cc2bwb75f80d8384c04db@mail.gmail.com \
--to=sqweek@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).