Knusbaum/remotewood

[knusbaum]

@rjkroege, Based on our discussion in #417, I created this proof-of-concept for editing things remotely in Edwood.

It's pretty rough, but it's somewhat working. I don't expect this to ever be merged, but wanted to get your opinion.

My export9p needs to be installed on the remote host, since it uses that to serve 9p back through ssh to edwood.

Commands are also run through ssh in a somewhat ugly way. The Setenv doesn't seem to work for me.

Forwarding a unix connection for $(namespace)/acme is required for win commands and other acme stuff to work, which I haven't included yet.

You should be able to test it with edwood -R "user@host:22"

[rjkroege]

I'll review this soon.

[xplshn]

How Soon is Now?

[rjkroege]

@xplshn: Edwood in a coma, I know.

This feature would be great but this patch has sort of fizzled out in a side discussion of the effect of "this is too intrusive architecturally" as written and it's not clear to me if/how it should be implemented. Clearly in a Plan9 context, this capability would be provided seamlessly by the OS. On MacOS, the high-road is to write a 9p storage provider (which I have started doing). On Linux, 9pfs or fuse would serve. But then there's windows...

Suggestions welcome.

[xplshn]

But then there's windows...

I don't think any person that knows about the existence of Plan9, actively practices its philosophy or uses the system cares about that tho. Its the minority among the minority.