tunneling through stdin/stdout, source routing

[David Woodhouse]

On Wed, 2006-11-15 at 00:54 +0100, Simon Richter wrote:
> In the particularly nasty setup I am facing here this is extra 
> difficult, as the same home directory is shared over multiple machines 
> of different architectures (and with different runtime libraries 
> installed), so I'd have to have the tool once for each architecture, and 
> find a way to properly switch on the architecture of the machine I'm 
> connecting to.
> 
> That's why I'd think a client-only solution would be the best solution 
> here. My client can always ask for a port forward, the server doesn't 
> care where it comes from.

That or a perl script to make a TCP connection?

If you also use multiple _clients_ then you still have the problem of
needing it compiled and installed for all machines.

-- 
dwmw2