On Tue, Jul 04, 2006 at 11:35:53PM -0500, Damon L. Chesser wrote:
> Bob Smither wrote:
> >This must be a FAQ, but I could not stumble upon a solution. With other
> >Linux boxen, I can ssh -X into them, then run X apps on the remote with
> >local display. On a newly installed Sarge Debian box, doi
On Tue, 04 Jul 2006 23:35:53 -0500
"Damon L. Chesser" <[EMAIL PROTECTED]> wrote:
> Bob Smither wrote:
> > This must be a FAQ, but I could not stumble upon a solution. With
> > other Linux boxen, I can ssh -X into them, then run X apps on the
> > remote with local display. On a newly installed Sa
On Tue, 04 Jul 2006 23:17:25 -0500
Bob Smither <[EMAIL PROTECTED]> wrote:
> Any suggestions as to why I can't run the remote app and see it
> locally?
Aloha,
Why not use vnc-server and vnc-client.
For instance, you could install tightvncserver (- virtual network
computing server software) on y
Bob Smither wrote:
This must be a FAQ, but I could not stumble upon a solution. With other
Linux boxen, I can ssh -X into them, then run X apps on the remote with
local display. On a newly installed Sarge Debian box, doing this
results in the following error:
Gtk-WARNING **: cannot open disp
On Tue, Jul 04, 2006 at 11:17:25PM -0500, Bob Smither wrote:
> Gtk-WARNING **: cannot open display:
>
> Any suggestions as to why I can't run the remote app and see it locally?
Has your remote box got 'X11Forwarding yes' in its /etc/ssh/sshd_config
file?
Cheers,
Paul.
--
Paul Dwerryhouse
This must be a FAQ, but I could not stumble upon a solution. With other
Linux boxen, I can ssh -X into them, then run X apps on the remote with
local display. On a newly installed Sarge Debian box, doing this
results in the following error:
Gtk-WARNING **: cannot open display:
Any suggestions
Incoming from Tim Connors:
> "Linux Nick" <[EMAIL PROTECTED]> said on Thu, 22 Apr 2004 15:27:14 -0400:
> >
> > Sorry top poster for life, not scrolling all the way to the bottom to =
> > get a
> > reply I know what the previous email said and don=92t need to read it =
> > again.
>
> I admire that
"Linux Nick" <[EMAIL PROTECTED]> said on Thu, 22 Apr 2004 15:27:14 -0400:
> This is a multi-part message in MIME format.
>
> --=_NextPart_000__01C4287E.4AEC3180
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> Sorry top poster for
Paul Johnson <[EMAIL PROTECTED]> said on Thu, 22 Apr 2004 11:11:02 -0700:
> diego <[EMAIL PROTECTED]> writes:
> > El jue, 22-04-2004 a las 08:52, Paul Johnson escribi=F3:
> >> DO NOT USE XHOST! xhost is considered harmful, use google for a few
> >> trillion reasons why. Just use ssh -C -X to get
"Linux Nick" <[EMAIL PROTECTED]> writes:
> Sorry top poster for life, not scrolling all the way to the bottom to get a
> reply I know what the previous email said and donʼt need to read it again.
You're supposed to trim your quoting, not quote the entire email. Cut
for context. Don't just turn
Chris Metzler wrote:
On Thu, 22 Apr 2004 15:27:14 -0400
"Linux Nick" <[EMAIL PROTECTED]> wrote:
Sorry top poster for life, not scrolling all the way to the bottom to
get a reply I know what the previous email said and don_t need to read
it again.
Yes, but it completely discourages *anyone*
On Thu, Apr 22, 2004 at 03:27:14PM -0400, Linux Nick wrote:
> Sorry top poster for life, not scrolling all the way to the bottom to get a
> reply I know what the previous email said and dont need to read it again.
>
I tend to agree with you. Sometimes, when the thread is long and
known, there i
On Thu, 22 Apr 2004 15:27:14 -0400
"Linux Nick" <[EMAIL PROTECTED]> wrote:
>
> Sorry top poster for life, not scrolling all the way to the bottom to
> get a reply I know what the previous email said and don_t need to read
> it again.
Yes, but it completely discourages *anyone* from jumping in late
On Thu, Apr 22, 2004 at 03:27:14PM -0400, Linux Nick wrote:
>
> [-- Autoview using /usr/bin/lynx -dump -force_html ''/tmp/mutt.html'' --]
>
>Sorry top poster for life, not scrolling all the way to the bottom to
>get a reply I know what the previous email said and don't need to read
>it
t;
To: diego
>
Cc: [EMAIL PROTECTED]
>
Subject: Re: Cannot launch remote apps on X
>
>
English is read from top down with the flow of context, not newest
>
information on top.
Please learn to quote accordingly.
>
http://learn.to/quote
>
http://ursine.ca/jargon/html/e
El jue, 22-04-2004 a las 20:11, Paul Johnson escribió:
> English is read from top down with the flow of context, not newest
> information on top. Please learn to quote accordingly.
> http://learn.to/quote
> http://ursine.ca/jargon/html/email-style.html
>
> You sent a private-mail reply to my atte
English is read from top down with the flow of context, not newest
information on top. Please learn to quote accordingly.
http://learn.to/quote
http://ursine.ca/jargon/html/email-style.html
You sent a private-mail reply to my attempt to help you on a mailing
list, and failed to mention having don
Yes there it is.
What is more strange is that even from the culprit machine it doesn't
work:
I do a ifconfig and it says 172.16.10.1 is one of its network interfaces
(no firewall active) so if I do:
export DISPLAY=:0 . ==> It shows up the window
export DISPLAY=172.16.10.1:0 ==> Complaints
Already changed. No luck this way...
Thanks for the hint anyway.
El jue, 22-04-2004 a las 07:45, George Cristian Birzan escribió:
> On Wed, Apr 21, 2004 at 11:32:48PM +0200, diego wrote:
> > Hello, I have a knoppix just installed and network configured with a
> > fixed IP (lets say 172.16.10.1) a
diego <[EMAIL PROTECTED]> writes:
> Hello, I have a knoppix just installed and network configured with a
> fixed IP (lets say 172.16.10.1) and working right. The problem is that
> if I do:
>
> 1) export DISPLAY=:0; xclock ==> It works
>
> 2) export DISPLAY=172.16.10.1; xclock ==> It cannot conn
On Wed, Apr 21, 2004 at 11:32:48PM +0200, diego wrote:
> Hello, I have a knoppix just installed and network configured with a
> fixed IP (lets say 172.16.10.1) and working right. The problem is that
> if I do:
>
> 1) export DISPLAY=:0; xclock ==> It works
>
> 2) export DISPLAY=172.16.10.1; xclo
Incoming from diego:
>
> El mié, 21-04-2004 a las 23:55, Monique Y. Mudama escribió:
> > On 2004-04-21, diego penned:
> > > Hello, I have a knoppix just installed and network configured with a
> > > fixed IP (lets say 172.16.10.1) and working right. The problem is that
> > > if I do:
> > >
> > > 1
Yes... sorry I made a typo, I meant:
...
export DISPLAY=172.16.10.1:0; xclock ==> It cannot connect to X
...
Anyway, thanks for pointing it out just in case...
El mié, 21-04-2004 a las 23:55, Monique Y. Mudama escribió:
> On 2004-04-21, diego penned:
> > Hello, I have a knoppix just installed
On 2004-04-21, diego penned:
> Hello, I have a knoppix just installed and network configured with a
> fixed IP (lets say 172.16.10.1) and working right. The problem is that
> if I do:
>
> 1) export DISPLAY=:0; xclock ==> It works
>
> 2) export DISPLAY=172.16.10.1; xclock ==> It cannot connect to
Hello, I have a knoppix just installed and network configured with a
fixed IP (lets say 172.16.10.1) and working right. The problem is that
if I do:
1) export DISPLAY=:0; xclock ==> It works
2) export DISPLAY=172.16.10.1; xclock ==> It cannot connect to X
I have done the "xhost +" part, also
Quoting Ethan Pierce ([EMAIL PROTECTED]):
> Id like to be able to run ftp and telnet to my home machine from
> work...normally this works fine. Today I thought I would just boot up my
> home machine to the login and leave it there to save some
> processor...theoretically this is supposed to wor
Definitely shouldn't work this way. Look in /etc{rcS.d, rc1.d, rc2.d, rc3.d}
and so on to see if they have a symbolic link to /etc/inetd (I think this
is the one you want) called Sinetd, where , are digits.
Then look in /etc/inittab to find out what runlevel you're at
before anyone logs in. (Runle
Id like to be able to run ftp and telnet to my home machine from
work...normally this works fine. Today I thought I would just boot up my home
machine to the login and leave it there to save some processor...theoretically
this is supposed to work? I called another friend (this is b4 I left for
Brad said:
> WindowMaker will do that. But, if you dock the new appicon that was
> created when you ran it with the ssh -f ... command, it should work ok
> then.
Got it! As I was responding to this, it occurred to me that the -f may
be what's causing the problem. When I drag over the appicon, th
-BEGIN PGP SIGNED MESSAGE-
On Tue, 21 Sep 1999, Dave Sherohman wrote:
> When I originally drag the appicon over to the dock, it runs there just
> fine, but if, for example, the appicon was for a
>
> ssh -f remotehost wmmon
>
> the dock icon's settings will show only
>
> wmmon
>
> and
I just got ssh set up and it works pretty slick, except for one little
detail... One of the things I wanted to be able to do with ssh is dock
apps running on other machines and have them restart automatically when
I log in. (i.e., have a wmmon for my local machine and another wmmon for
a remote m
31 matches
Mail list logo
