rminnich/go9p

Go9p but done in a way that works with goinstall

This is go9p done in a way that I can understand.

To install: export GOPATH=~rminnich/go go get -a github.com/rminnich/go9p go get -a github.com/rminnich/go9p/ufs go install -a github.com/rminnich/go9p/ufs

~/go/bin/ufs

go9p's Issues

Summary of implemented fs

Could you add a little summary of what the different implemented filesystems are? I can't really tell just by browsing what ufs is for example.

Mount (without auth) requires nuname

I'm not sure if this is a bug. But the behavior surprised me, and it means I can't use srv_fcall.go with the 9p that comes with Plan 9 from Userspace.

I'm working on a file system that enforces file access permissions for virtual users. The users are defined in the file /adm/users, and don't need to authenticate just be authorized (https://github.com/mbucc/vufs/blob/master/vusers.go).

When 9p tries to mount with authentication (9p -n -a localhost:5640 ls), it sends a zero for nuname:

Tattach tag 0 fid 0 afid 4294967295 uname 'mark' nuname 0 aname ''

Since nuname != NOUID, srv_fcall.attach checks Uid2User, which fails, as the 0 doesn't match my virtual user's uid defined in adm/users. (I suspect 9p will always send a 0 for nuname in this case.)

Would you be interested in a patch that modifies the user lookup logic to check Uname2User before Uid2User for non-dotu situation?

Does not work with golang.org/x/websocket

I've been trying to get go9p up and running over a websocket connection for some time and have had no luck. I can't get the Ufs server to run over websockets. I'm not sure how else it could be set up. I either get a "Connection reset by peer" error, or a EOF error on the client. I have a feeling that this has to with how websockets handles its message frames. The proof of concept server and clnt I set up are in the below gist. Any guidance of how to set it up correctly or where to start tracking down the 'bug' would be great.

https://gist.github.com/cleahcim/c0f43caabc346473f7ea