Linked by Thom Holwerda on Mon 12th Jun 2006 13:43 UTC, submitted by Neal Freemen
Permalink for comment 132832
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
Linked by Thom Holwerda on 05/15/13 23:03 UTC
More News »
Sponsored Links



Member since:
2006-02-04
But still, if I'd want to administrate my Linux server graphically, I could always install X, start it and remotely launch any GUI tool which is on the server and have it displayed on my client machine. But this is _optional_, and I can turn the whole GUI functionally on and off whenever I want, minimizing resource usage
Actually, the server itself does not need X, XDM or anything else installed or running. If you install any X app on the server you can log in via ssh from a system running an X server, launch the app on the server and display it on the client. The X display system does not require any local X components to do this. The X app(running on the server) just needs an X server somewhere to display to. That can be local or remote.
This method is also somewhat like a thin client setup, with the exception that the client does not boot from the server. A thin client server only needs to run XDM or equivilant.