You are very close with the definitions you used. The
only changes I would suggest is that the PC is
actually running the X-server because it's serving up
its screen, keyboard and mouse. The system running
the X-windows system is actually called the X-client
because it runs the applications. The
-
From: Joel Hammer [mailto:[EMAIL PROTECTED]]
Sent: Saturday, February 01, 2003 3:01 PM
To: [EMAIL PROTECTED]
Subject: Re: Windows client, linux X server
I wasn't aware that a windows client could log on to the LTS.
I thought that required linux on the client, or, at least a reboot w
On Sat, 1 Feb 2003 14:06:13 -0500
Tim Wunder <[EMAIL PROTECTED]> wrote:
> On Saturday 01 February 2003 1:43 pm, someone claiming to be Joel
> Hammer wrote:
> > I would like to run X client sessions from windows clients to a
> > linux server.
> >
> > I hope I have this terminology right. The distin
I wasn't aware that a windows client could log on to the LTS.
I thought that required linux on the client, or, at least a reboot with
a special boot disk.
Joel
On Sat, Feb 01, 2003 at 02:52:39PM -0500, Wil McGilvery wrote:
> I would think that the Linux Terminal Server would work well for this s
]]
Sent: Saturday, February 01, 2003 2:12 PM
To: [EMAIL PROTECTED]
Subject: Re: Windows client, linux X server
I should have added that if you need remote X access
for many users; there are probably much better
solutions. Each user who wants to use tightvnc or vnc
must start a separate instance of the
I should have added that if you need remote X access
for many users; there are probably much better
solutions. Each user who wants to use tightvnc or vnc
must start a separate instance of the server.
Andrew
--- Andrew Gould <[EMAIL PROTECTED]> wrote:
> I like tightvnc (or vnc). Each user can ha
On Saturday 01 February 2003 1:43 pm, someone claiming to be Joel Hammer
wrote:
> I would like to run X client sessions from windows clients to a linux
> server.
>
> I hope I have this terminology right. The distinction between client and
> server in this situation always befuddles me, but, I thin
I like tightvnc (or vnc). Each user can have his/her
own uniquely configured session; and this can be
different from the desktop that would appear if the
user was logging in locally. For example, on a server
at work, I can log into a KDE desktop; but when I use
tightvnc to login remotely, I use s
