I think we should take a step back, and level set based on a question in the first post in the thread, as there may be some confusion.
Quote:
Originally Posted by spermwhale_warrior
The question was to begin with, why 'X > /dev/null 2>&1' doesn't nullify the graphical ouput, as I thought it was just in the end an virtual terminal made busy with pictures.
|
The
X Window System is a ... well ... it is a
system for graphical manipulation and display. It does not use standard files -- or named files -- for data movement between application and display. Instead, it uses
network sockets, as shown in the graphic I included earlier in this thread, for communication between X Client (the graphical application) and X Server (human interfaces). The X Server communicates via hardware drivers with hardware: keybaords, mice, displays, and other devices.
X Clients may or may not use standard files. They are optional.
To add some confusion, among X Client applications are terminal (tty) emulators such as
xterm. These are used to run interactive shells, which may include manipulating applications that use standard files -- whether these applications happen to be other X Clients or not.