public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: x11 not working on ssh
Date: Sat, 25 Feb 2006 10:48:19 -0700	[thread overview]
Message-ID: <pan.2006.02.25.17.48.18.793852@cox.net> (raw)
In-Reply-To: 200602251330.49802.volker.armin.hemmann@tu-clausthal.de

Hemmann, Volker Armin posted
<200602251330.49802.volker.armin.hemmann@tu-clausthal.de>, excerpted
below,  on Sat, 25 Feb 2006 13:30:49 +0100:

> On Saturday 25 February 2006 11:31, Kevin F. Quinn (Gentoo) wrote:
>> On Fri, 24 Feb 2006 20:44:19 +0100
>>
>> If you're forwarding X clients through ssh, it all works fine with
>> '-nolisten tcp', since as far as the server is concerned the clients
>> are local.
> 
> ah, ok, nice to know.
> 
> I never was interessted in X forwarding. So I learnt something today ;)

Same here.  =8^)  Makes perfect sense, but I never stopped to think
about it beyond the obvious, since I've never had need for it.  Now I
know just in case I ever do.  Thanks!  =8^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2006-02-25 17:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24 15:47 [gentoo-amd64] x11 not working on ssh Gavin Seddon
2006-02-24 19:44 ` Hemmann, Volker Armin
2006-02-25  5:45   ` Mike Doty
2006-02-25 10:31   ` Kevin F. Quinn (Gentoo)
2006-02-25 12:30     ` Hemmann, Volker Armin
2006-02-25 17:48       ` Duncan [this message]
2006-02-25 13:16   ` Gavin Seddon
2006-02-25 16:01     ` Joerg Gollnick
2006-02-27 11:03       ` Gavin Seddon
2006-02-27 11:28         ` Gavin Seddon
2006-02-27 13:08           ` Brett Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pan.2006.02.25.17.48.18.793852@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox