-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Brian Dessent wrote:
> It's not a matter of porting per se. You can use x.org R7 with Cygwin
> right now, through Cygwin Ports. (But that's of course a separate
> project so use its mailing list for problems.) The issue is that Cygwin
> currently
Ruth Ivimey-Cook schrieb:
> There is another option: set up an LBX connection. This requires a process
> (called LBX) that runs on the machine running the normal X server; you then
> connect your clients to LBX.
>
> LBX is "Low Bandwidth X" and is a protocol-specific compression algorithm
> whi
On Sat, Feb 10, 2007 at 02:48:45PM -0800, Brian Dessent wrote:
>Ruth Ivimey-Cook wrote:
>
>> Is anyone considering porting cygwin/x to the v7 architecture?
>
>It's not a matter of porting per se. You can use x.org R7 with Cygwin
>right now, through Cygwin Ports. (But that's of course a separate
>
Ruth Ivimey-Cook wrote:
> Is anyone considering porting cygwin/x to the v7 architecture?
It's not a matter of porting per se. You can use x.org R7 with Cygwin
right now, through Cygwin Ports. (But that's of course a separate
project so use its mailing list for problems.) The issue is that Cygw
Folks,
Is anyone considering porting cygwin/x to the v7 architecture?
Ruth
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/f
> The encryption doesn't matter. It is the latency of your
> connection that matters (ping time), because the X proctocol
> isn't very efficient.
There is another option: set up an LBX connection. This requires a process
(called LBX) that runs on the machine running the normal X server; you
