On Jan 14, 2008 6:56 PM, <[EMAIL PROTECTED]> 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/
