public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Bambach <eric@cisu.net>
To: "S. Barret Dolph" <wheds8@ms66.hinet.net>
Cc: linux <linux-newbie@vger.kernel.org>
Subject: Re: remote admin
Date: Thu, 14 Apr 2005 10:40:01 -0500	[thread overview]
Message-ID: <200504141040.02011.eric@cisu.net> (raw)
In-Reply-To: <200504142239.24316.wheds8@ms66.hinet.net>

Ssh is the de facto standard for remote administration but It lacks the 
ability to give you a GUI interface. SSH Is quick and dirty remote 
administration and comes standard (or should ) on all Unix variants. 
(openssh.com)

TightVNC is a rather "unrobust" remote X server but it gets the job done. This 
will let you connect remotely and get an X GUI session open.

If you can afford it, try to look into NXMachine (No Machine) remote 
administration. It offers very robust and configurable remote X server 
connections that are compressed and secured. This can be used over low 
bandwidth connections because it uses caching and compression. As far as I 
remember, they offer single user single machine trial liscenses so you can 
test drive the technology before buying and I dont think that the licenses 
are terribly expensive.

HTH!

On Friday 15 April 2005 12:39 am, S. Barret Dolph wrote:
> I would like to be able to do some admin stuff on our school computers from
> home. What is best way to do this? Are programs such as "Webmin" better
> than remote logins or just different. The administrative tasks are usually
> more school administration than computer administration but not always just
> that. For example, I am now working on getting chinese input on our school
> computer. School administration work is usually just things like updating
> documents and making sure that the latest materials are available to them.
>
> Cordially,
> S. Barret Dolph
> Taipei Taiwan
> -
> 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

  parent reply	other threads:[~2005-04-14 15:40 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 [this message]
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
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=200504141040.02011.eric@cisu.net \
    --to=eric@cisu.net \
    --cc=linux-newbie@vger.kernel.org \
    --cc=wheds8@ms66.hinet.net \
    /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