On Mon, Jun 16, 2003 at 03:51:15PM -0500, Richard Troth wrote: > When your users mention CYGWIN, > clearly they're after X (server) on Windows boxes > with XDMCP access to your Linux host(s). Strictly speaking, > X on Linux is then the CLIENT, even though the host is > considered to be a server. CYGWIN XFree86, like other X-on-Windows, > will use the XDMCP protocol to establish a session. But the server > (the X server) is on the PC, not on the mainframe (nor on the > remote PC). Still, they will get a sign-on effect as if their > PC were the client. And in sign-on semantics, it is the client.
Why xdmcp? This means that thy have to run the whole X desktop on the server. This means much more traffic on the network. Why not let them run just the programs they need? Instead they could start a cygwin shell and run: cygwin$ ssh -x linux_server linux_server$ the_program_they_need For optimal results you may share the cygwin home directory with the linux home directory (using the cygwin 'mount', and samba). Something similar to single-sign-on can be achived using ssh keys, unless you have anything better. The X server can be any other server, mind you. -- Tzafrir Cohen +---------------------------+ http://www.technion.ac.il/~tzafrir/ |vim is a mutt's best friend| mailto:[EMAIL PROTECTED] +---------------------------+
