X-Window is basically a server daemon (software package) that generates a graphical environment for the software that you want
to run, & displays it to you in your accustomed "graphical" (I refrain from using the word windows) form. This does not only apply to
software that you run locally, you can also utilise a graphical X server daemon over a network, even over the internet, & have the software running
on this remote computer displayed in this graphical environment. Providing that is that the remote computer has an X server
daemon running. This feature has absolutely no drawbacks when you are using Linux on your own computer, in a sort of "Workstation",
but there can be a problem if you have a configured & running X server on a physical server computer. This is the reason that I have no
X server daemon on my Linux server, but it is installed on the other Linux/Windows computer. The reason for this is security!
Lets say that I did have a running X server running on my Linux server, which is permanently connected to the internet & therefore partially accessible
(depending naturally on which types of communication that I let into the server) from anywhere in the world. I could happen if
someone "broke into" the machine that they were able to see exactly what I was doing on the server. When I say "see" I mean that
literally!! It would be as though they had just plugged their computer monitor into my graphic card! They would see every key that was
pressed, every mouse movement, literally EVERYTHING. Not such a good idea huh :o)
I think it's a very important point that has to be mentioned when building your own Linux server, & now you can see why I had
to do this whole "project" in the TUI (Text User Interface) mode, all those hardcore commands, & no pretty pictures. It was not easy
but I think you actually learn more about Linux in this type of use than you do with the "push all the funky buttons" approach.
