public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Bambach <eric@cisu.net>
To: qwms-avib@dea.spamcon.org
Cc: hgf4-wgsm@dea.spamcon.org, Linux-Newbie <linux-newbie@vger.kernel.org>
Subject: Re: remote admin
Date: Thu, 14 Apr 2005 16:02:15 -0500	[thread overview]
Message-ID: <200504141602.15453.eric@cisu.net> (raw)
In-Reply-To: <20050415074715.5845d80b.qwms-avib@dea.spamcon.org>

On Thursday 14 April 2005 02:47 pm, qwms-avib@dea.spamcon.org wrote:
> Eric Bambach wrote:
> > Ssh is the de facto standard for remote administration
> > but It lacks the ability to give you a GUI interface.
>
> Getting a GUI interface for ssh is easy.  Simply start
> ssh from an xterm, login to the remote server and execute
> xterm.  This will cause a remote xterm to appear on your
> local X display.
>
> Instead of a remote xterm, you can start a remote
> window manager (or other X application) the same way.

Hehe, I stand corrected. I suppose *I* usually think of it as more of a 
console administration app. Anyways, this is not a good solution if you are 
logging in from a windows or "other" OS based machine. You would have to 
install a local X-server which may or may not be practical or useful.

Additionally, as others pointed out you can tunnel X connections over SSH. 
While this is true the X protocol by itself is quite heavy and lag and 
interactivity will be less than spectacular on anything less than 10Mbit. 
This is why I suggested NX Server for GUI administration because it does some 
quite spectacular compression and caching I havent seen in other projects 
(though I admit I havent done alot of diggin on the subject, only raw X, 
lbxproxy, ssh compression, and VNC each of which has its own caveats)
> Cheers,
> Steven
>
>
>
>
>
>
> ____________________________
> http://www.basiclinux.com.ru
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs

-- 
----------------------------------------
--EB

> All is fine except that I can reliably "oops" it simply by trying to read
> from /proc/apm (e.g. cat /proc/apm).
> oops output and ksymoops-2.3.4 output is attached.
> Is there anything else I can contribute?

The latitude and longtitude of the bios writers current position, and
a ballistic missile.

                --Alan Cox LKML-December 08,2000 

----------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2005-04-14 21:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-15  5:39 remote admin S. Barret Dolph
2005-04-14 15:26 ` Ray Olszewski
2005-04-14 15:40 ` Eric Bambach
2005-04-14 16:22   ` Ray Olszewski
2005-04-14 17:14   ` J.
2005-04-14 18:02     ` Ray Olszewski
2005-04-14 21:58       ` J.
2005-04-14 21:15     ` Eric Bambach
2005-04-14 19:47   ` qwms-avib
2005-04-14 21:02     ` Eric Bambach [this message]
2005-04-15 14:05       ` Peter
  -- strict thread matches above, loose matches on Subject: below --
2005-04-14 15:28 Little, Chris

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=200504141602.15453.eric@cisu.net \
    --to=eric@cisu.net \
    --cc=hgf4-wgsm@dea.spamcon.org \
    --cc=linux-newbie@vger.kernel.org \
    --cc=qwms-avib@dea.spamcon.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