Is it that you have always been confused when XWindow is running? In the end is the server, that is the client? How is it getting more and more?
OK, don't understand first, come with me, you can understand after you do it, you can understand it.
First of all, there is a Linux machine, now there are so many virtual machine programs, how do you should have a piece of Linux in your windows? I used Linux.
After that, you still need a XWindow server, in fact, Linux has been bringing, but in order to thoroughly understand this, we still first download a cygwin, then install it to Windows, pay attention to the full stuff under xpackage. All installed.
Ok, the system is ready, we start:
First enter Cygwin under WIN, then start the XServer server with instruction x &.
After linux, use xterm -display windows_ip: 0 &, at this time there is an XTERM window in Cygwin. You can enter various instructions, but the window cannot move, change the size, and the like.
Of course, you can also enter XClock -Display Windows_IP: 0 & etc. in Linux, you can also launch the xterm window multiple times, but the XTERM that is started will overwrite the previously started, so you can't switch to the original xterm window. in.
Why is this so? This is because there is no window manager, that is, there is no GNOME, KDE, FVWM, and TWM procedural to manage these windows.
Enter gnome-session in the XTERM window (you can also enter TWM, Start-KDE).
How? What is your familiar gnome window appears?
In fact, the procedures you start under Gnome are also ordinary executables, you can see / sur / bin / gnome *, at this time, you enter GNOME-ABOUT under a xterm, GNOME's About window appeared?
What? You still don't know that is the server, that is the client?
Ok, then we enter XClock -display localhost: 0 &, then switch to Cygwin's X window, how about switching to Cygwin's X window, how? No XCLOCK window?
