Re: [SLUG] Remote X,...Ding!!!, Round 2

From: Vernon (vsingleton@cfl.rr.com)
Date: Thu Feb 13 2003 - 06:16:29 EST


John wrote:

>I was trying to use one monitor to display the graphical desktop
>environments of two Linux boxes.
>

Ok ... i tried it again, just to refresh my memory.

First of all one thing to try as root is
"startx -- :1"

That should bring up kde in display 1.
If root's home directory has an .xinitrc file all bets are off.
If there is such a file delete it before trying the command above.

Now ... go ahead an log out of the kde which started in display 1

Ok now, if you want to start kde in display :1 off of a remote machine
the way that I did it tonight was ...

1. Ensured that as root "ssh user@remote" logged me in _without_ a
password or passphrase.
If you cannot do that, we need to have a different lesson, just about
that. So, given that
"ssh user@remote" logs you into the remote box without a password, we
can go on to step 2.
Note also that we want to ssh from root on local machine to "user" (not
root) on the remote machine.
root works also (i tried it), but it is not recommended to log into kde
as root.

2. Create a file in root's home directory on the local machine called
".xinitrc" with the following
contents "ssh -X user@remote startkde"

3. execute the following command as root on the local machine
"startx -- :1"

Now I did have to "toggle" back and forth from display 0 to 1 a few
times ...
it did not seem very stable ... once it seemed to loose the connection,
but I just killed the "X :1" process
on the local machine and reexecuted "startx -- :1", and it worked.

I toggled back and forth between display 0 and 1 several times using
cntrl-alt-F7 and cntrl-alt-F8
respectively, launched mozilla from display 1 (remote machine), browsed
the web with now problems,
killed the "X :1" process again, and restarted it with the "startx --
:1" command again, washed, rinsed,
repeated, without a hitch, several times. I only had a problem once,
but i just killed and restarted the
"X :1" process, and restarted it, and it was fine after that ... must
have been a connection issue.

Hope that helps.
Vernon



This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 15:17:12 EDT