Sorry, I'm tired, long day, but this discussion is not making sense to me. I hope I don't make anyone mad at me :-)
9vx can accept connections today, with or without the ether device. I've used 9vx to export root file systems to ARMs. It's how I bootstrapped my openrd. Now, there is this business in Unix called privileged ports. If you want to export port 564, then you must run 9vx as root. Problem solved. Listen1 is quite fun and handy for this kind of tinkering around. Also, you can trace all the 9vx network activity on many unixes: strace -etrace=network 9vx etc. etc. And see where things go sour. The only issue is that if your 9vx host is using a port (e.g. 22) then 9vx can't export on that port, because the 9vx port space and the host os port space are shared. As for 9vx forks on bitbucket: we're all good with hierarchical name spaces, right? I mean, yiyus/9vx and rminnich/9vx are not the same thing. I'm not usually in a hurry to pull from yiyus, because I've felt no urgency to do so, If you want me to try something, let me know. Bitbucket has worked very well for me across a lot of projects. So has hg in general. They're both great, and they work well from Plan 9. Don't like em? Don't use 'em ;-) ron
