I like ssh because you can do X forwarding in one command

ssh -X username@hostmachine

Then you can start you X programs with out having to modify environment
variables.=20

-----Original Message-----
From: port-macppc-owner@NetBSD.org [mailto:port-macppc-owner@NetBSD.org]
On Behalf Of William Duke
Sent: Monday, November 21, 2005 12:00 PM
To: Peter Seebach; port-macppc@NetBSD.org
Subject: Re: Unofficial macppc 2.1 ISO for old world machines=20



> From: seebs@plethora.net (Peter Seebach)
> Reply-To: seebs@plethora.net (Peter Seebach)
> Date: Mon, 21 Nov 2005 11:47:57 -0600
> To: port-macppc@NetBSD.org
> Subject: Re: Unofficial macppc 2.1 ISO for old world machines
>=20
> In message <BFA771EA.4D23%wduke@cogeco.ca>, William Duke writes:
>> What about ssl or ssh?
>=20
> ssh offers a good replacement for telnet.
>=20
>> Now, If you were running big bad important servers that the security
of the
>> nation were dependent on, then telnet might not be the solution for
you.
>> If, however, you're a newbie to unix or you're just playing with the
darn
>> things for something to do, as many folk are with these old 68k and
ppc
>> machines, security probably isn't going to be a big concern for you.
I
>> mean, world war three isn't going to be started by little Johnny
>> compromising the security of little Jimmy's G3 Powermac.
>=20
> Yes, but bad security is habit-forming.

I use telnet all the time.  However, my network is behind a firewall and
comprises about four or five old ppc and 68k machines, and contain no
data
of any significance.  Truth be told, I don't even bother with backups on
these machines.  Reason:  ROI.   The return on my time & energy
investment
is virtually nil because I have nothing on these machines that "cannot"
be
lost.

Perhaps my situation is unique, but that's unlikely.  I will routinely
format my drives just to install something new or different.  They're
playthings for me.  Nothing more and nothing less.