Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have been doing some reading on X11 stuff and have come with something I want to try with remote servers. Unfortunately, the reading I have been doing is confusing me.
I have managed to find lots of information that talks about setting stuff up (getting an environment up and running). I am looking for a more generic explanation (I want to know why stuff works the way it does).
I would really appreciate three things:
1. A general explanation of the XServer/Client architecture.
2. An answer: Does the window manager have to be running on the same computer as the server (I'm getting conflicting information).
3. Most importantly, a good reference that I can keep looking in on when I get more questions (or that answers these questions).
As I understand it (and I don't really):
Client: Whatever Window Manager (kde, gnome, and others)
Based on this I should be able to install them on different machines, tell the server to listen on a port and tell the client to check that IP/Port.
X Server - program that serves up the display of the computer on which it runs. Clients connect, and use the server to display things, and also talk amongst themselves etc.
Window manager - special kind of client responsible for managing other "normal" clients. It can be run from any computer, although if remote it'd be a bit slow. Normally it's run locally, there simply is rarely any good reason to run it remotely.
Client: anything else basically
There isn't really much more to it than that. X is sometimes used for primitive IPC. Umm, oh, X has security built in as well. The DISPLAY variable controls which server it tries to connect to.
Finally, when the client and server are on the same machine, they use various fun optimizations to speed things up.
What do you mean by "other 'normal' clients"?
The window manager can be run from a remote location (server/manager on one box, user sitting at a different one)?
So basically, it would not be difficult to set the server up on one machine (IP: 220.127.116.11) and have a window manager on another (IP: 321.321.321.321). Then have the window manager talk to the server on the other machine? Is there anything that would have to go between these two pieces (other than a network cable )?
Normal clients are your programs, web browser, gimp etc etc
IPC = interprocess communication, ie apps talking to each other
The server is usually run on the machine you are sitting in front of, as it "serves" up the display hardware. Although you can run a server on one machine, and display it on another, that involves using third party remoting protocols and generally abusing X in ways it wasn't designed for, so pretend you just have to run the X server on your local machine.
X communicates via TCP/IP when over a network, so you just need a properly setup cable and network. It can run via the net as well, albiet slowly
Thanks. That was where I was going with this (sort of) and that looks like it might be the best I have seen along those lines so far. But I hate it when things don't make sense so now I am obsessed with understanding this system (that way I can abuse it later ).
Thank-you. You've been very helpful.
I did read somewhere (can't remeber where) that the system was designed the way it was so that you could application serve to other machines (run gimp on the server box w/ xserver, and run window manager on user's box and see gimp there).
Other places have described that the minute you want to do something like that, you need a server on the local machine and the server talks to the remote machine. That configuration seems to me to defeat the purpose I had read at the first place.
I'm probably frustrating people already. It doesn't usually take me very long to do that . Does anyone know of any good reading on the subject that will keep me out of your hair for a week or two?
Too often on forums, people aren't willing to talk concept. I've had people get REALLY offended that I didn't take their solution to my problem. This has been refreshing. Someone willing to help with me wanting to understand rather than just "Here is how you fix it".
david_ross, thank you as well.
After all of that discussion. I think I know what I want to be playing with and how I want to play with it. I have a feeling that it will end up being some comparisons between configurations. At least on of those configurations will involve LTSP. That's a great system.
Again thank-you both.
One last request... reading recomendations (the more technically detailed the better)?