>From wikipedia (http://en.wikipedia.org/wiki/X_Window_System): X uses a client-server model: an X server communicates with various client programs. The server accepts requests for graphical output (windows) and sends back user input (from keyboard, mouse, or touchscreen). The server may function as: *an application displaying to a window of another display system *a system program controlling the video output of a PC *a dedicated piece of hardware. This client-server terminology - the user's terminal as the "server", the remote or local applications as the "clients" - often confuses new X users, because the terms appear reversed. But X takes the perspective of the program, rather than that of the end-user or of the hardware: the local X display provides display services to programs, so it acts as a server; any remote program uses these services, thus it acts as a client. -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of mark Sent: Sunday, September 21, 2008 11:21 AM To: lists@xxxxxxxxxxxx; General Red Hat Linux discussion list Subject: Re: Virtualizing KDE's Terminology: as I mentioned, X terminology is absolutely the opposite of the way *every* other usage of it is. If it were a d/b, in X terminology, the d/b server would be the client, and the machines calling it would be the servers. Wrapped your head around that? No, as far as I'm concerned, it makes no sense either, but that's what they did at MIT in the eighties.... -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
