... coffee hasn't kicked in yet, so coherence is optional ... On Sat, 19 Jan 2008, Les Mikesell wrote: > Paul Johnson wrote: > > On Jan 9, 2008 2:54 AM, Alexander Apprich > > <a.apprich@xxxxxxxxxxxxxxxxxxxx> wrote: > > > Robert P. J. Day wrote: > > > > yes, yes, it's really basic stuff but ... > > I found this to be informative. > > > > I've not used vnc for about 10 years, since Windows 95. > > > > It works differently than I remember. In the old days, when I would > > use vnc, I would see the programs that were running on the other > > system, and I'd take control of the keyboard and mouse of the other > > system. It was handy for practical jokes where we would make people's > > PCs do crazy stuff. > > > > In this vnc on Fedora, I see a blank desktop, rather than a running > > session on the other PC. by "blank desktop", do you mean truly blank, or just a regular initial desktop with no clients running on it yet? i'm assuming the latter. > > What's the story there? > > Linux can run multiple sessions, so there are several ways to run > the vnc service. One is to use vncserver to start separate > long-running sessions that are not attached to the console. That > is, you can connect, start some programs, disconnect, then reconnect > later, perhaps from a different view and the programs will still be > running. Another way is to set up xinetd to start new sessions for > each connections which will be destroyed as you disconnect. Yet > another is with an X module that allows you to connect to the > console session, more or less like the windows version where that > was the only available session. i, too, recall the days when a VNC session would take over a remote desktop but i didn't get into that in the recipe. i can't test this at the moment but i'm going to hazard a guess as to how things work. if someone is actually logged on to the remote linux system, then they're running an X session corresponding to display :0. when someone on that remote system runs "vncserver", they should get a new X session on display :1 and that's the one you're connecting to, so that represents a new X session entirely independent from the one the user on the remote system is actually working with. if you wanted to grab control of their desktop, i imagine you'd have to do something corresponding to running vncviewer and connection to display :0. is that even possible? i didn't look into that. does any of the above make sense? clarification, anyone? rday p.s. as mike points out, it would seem that, since windows supported only one X session in the first place, that would be the one you were connecting to. -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA Home page: http://crashcourse.ca Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook ========================================================================
