X-windows is a standard for displaying application User Interfaces on a remote dislay. It uses a client/server model with following components.
X display server | Where the display is (Xserver, Exceed, ReflexionX, Viewnow) |
X client | The application to be displayed (e.g. xterm). |
Windows Manager | The application on the server managing the user session (CDE, Gnome, KDE). Buttons, icons, window borders are part of the window manager. |
Fontserver | Server which provides the display server with the correct fonts for the application. |
- DISPLAY
- Variable pointing to where X should put its windows. It has the form:
<Address>:<display>.<screen>, Usually
<hostname>:0.0A client system can run several X-hosts with different display
numbers. Display can consist of more then one screen. - xev
- Opens a window, all events in this window (eg keystrokes) are dumped to
stdout.Look in /usr/X/demo
Tips and Tricks
- xterm
- Start an X-windows terminal. A terminal started from an X-windows manager session does not start the shell as an interactive shell automatically. This means it does not invoke /etc/profile. In gome-terminal you should select ‘Run command as a login shell’ in the ‘Title and Command’ tab in the current profile.
- kdeinit
- KDE process launcher. Sometimes launching programs in KDE report: “Cannot talk to klauncher”. This can be fixed by restarting the thing:
# dcopserver_shutdown
# kdeinit
Additionally you may need to remove all .DCOPserver_* file in your home directory just before starting kdeinit.