Prev: Nvidia Graphic card driver problems
Next: See and Enjoy Indian Girls Gallery.
From: taco on 31 May 2010 03:13
houghi wrote:

> taco wrote:
>> It's not that difficult....
>> ssh -X myserver
>
> I start with e.g.
> `ssh -X -o "UserKnownHostsFile /dev/null" -p 2222 houghi(a)localhost`
>
>> xterm &
>
> I am already in a terminal session. Running another terminal should (and
> does not) make any differce. Just to be sure, I tried it out and ran the
> above non needed step. The result is identical.
>
>> and in xterm you simply start firefox.
>> (firefox should not run on your local machine).
>

Sorry i don't understand the logic of starting a ssh session to localhost,
and it's also different from what you posted before. Anyway, I think you
don't understand a few basic things about X. X is a client-server system,
although it's a bit twisted on which is server and which client in the
architecture. The display environment variable refers to the X11 server
screen. It gives what display server will receive the output generated by
the application run on the client. For a session you can specify where the
output will appear. Using the xterm command makes tweaking of the
xhost/display environment variable easier. And, yes, it DOES make a
difference.
Do a lookup on the terms xhost, display environment, xterm and read/learn
some basic linux stuff.
Example first link in google:
http://www.cisl.ucar.edu/docs/ssh/guide/node29.html
taco
From: JT on 31 May 2010 05:22
On 31/05/10 10:50, houghi wrote:
> taco wrote:
>
>>> I start with e.g.
>>> `ssh -X -o "UserKnownHostsFile /dev/null" -p 2222 houghi(a)localhost`
>>>
>> Sorry i don't understand the logic of starting a ssh session to localhost,
>>
> The port 2222 is a tunnel to port 22 on a Virtualbox. So it is not
> really a ssh to localhost.
>
>
So you're tunneling through another tunnel.... Mmm, didn't get that
before. It might then be that VirtualBox's network stack is the problem
and not ssh. On my two physical machines it did not reproduce, so maybe
we're looking the wrong way? VB has several very distinct methods of
setting up networks. Maybe you could try giving it a 'real' network
address (i.e. make it really visible as a seperate machine on your
network) - I believe the option in VB is 'NAT' - and then try to
reproduce again.

And of course, make sure that the ~/ is not mapped by VB to your host's
/home/ ;-)
>> and it's also different from what you posted before.
>>
> In what way? `ssh -X user(a)virtualbox` is what I do The -o is so the
> signature is not placed in ~/.ssh and that means you need to type "yes"
> each time. -p 2222 houghi(a)localhost is the same as houghi(a)virtualbox.
>
>
>> Anyway, I think you
>> don't understand a few basic things about X. X is a client-server system,
>> although it's a bit twisted on which is server and which client in the
>> architecture.
>>
> I am sure of that. What want is software to behave like all the other
> software.
>
>
>> The display environment variable refers to the X11 server
>> screen. It gives what display server will receive the output generated by
>> the application run on the client. For a session you can specify where the
>> output will appear. Using the xterm command makes tweaking of the
>> xhost/display environment variable easier. And, yes, it DOES make a
>> difference.
>>
> Well, It does not in my case. What my worry is, is not that I am unable
> to get it running as I like. The problem I have is that all the software
> runs in one way and Firefox runs in another way. I have no interest in
> whatever excuses they have. It does not behave as expected and that can
> be dangerous.
>
>
>> Do a lookup on the terms xhost, display environment, xterm and read/learn
>> some basic linux stuff.
>> Example first link in google:
>> http://www.cisl.ucar.edu/docs/ssh/guide/node29.html
>>
> That is nice, as it shows that there is no difference in wether I run
> xterm or not. I CAN forward X (with the -X option) so there is no issue
> there. I CAN run it as the remote user with the option. The problem I
> have is NOT with ssh or forwarding, the problem I have is with how
> Firefox handles stuff. And that goes beyond ssh.
>
> houghi
>


--
Kind regards, JT

From: Eef Hartman on 31 May 2010 06:00
Jan Gerrit Kootstra <jan.gerrit(a)kootstra.org.uk> wrote:
> I only saw the things happening what Houghi describes when running both
> a local and a remote firefox at the same time.

That is documented behaviour: if you already got a (local) firefox
running ANY new invocation of firefox (even through ssh -X) will start
another window within THAT instance of firefox, not a separate startup.
--
******************************************************************
** Eef Hartman, Delft University of Technology, dept. SSC/ICT **
** e-mail: E.J.M.Hartman(a)tudelft.nl - phone: +31-15-27 82525 **
******************************************************************
 | 
Pages: 1
Prev: Nvidia Graphic card driver problems
Next: See and Enjoy Indian Girls Gallery.