6 May
2002
6 May
'02
11:33 a.m.
While I agree there is plenty of room for preferences, I don't see why one
would want everything isolated from everything else on the LAN, when the
existence of the LAN is warranted by the need for shared access. ON top of
that, typing half a screenful of text just to make some file on some other
machine accessible seems a mite burdensome. Even under DOS it only takes a
single half-line of text.
Some people just like *NIX because it enables them to stroke their own need
for pseudo-sophistry.
Dick
----- Original Message -----
From: "Raymond Moyers" <rmoyers(a)nop.org>
To: <classiccmp(a)classiccmp.org>
Sent: Monday, May 06, 2002 5:11 PM
Subject: Re: APPLEVISION Monitor,, No shell = No power
On Monday 06 May 2002 16:36, you wrote:
Maybe they're willing to type a couple lines
for the sake of
the added reliability, maybe it's easier for them to type
it out than to grab the mouse...
Or perhaps if your already in the all powerfull environment
you would only leave when the task isn't suited or
the expense in time/effort/bother of moving to the other
interface is less than staying put.
some command strings become buttons.
This button starts CDE desktop on my Sun, and places it windowed
onto my Windomaker/Linux desktop as if it was an application
("SunDT :2 root@Sparc", SHEXEC, "(Xnest :2 -display fubar:0
-nolock -bs -su &) && ssh1 -a -x -k -n -P -q -l root Sparc
'(/root/xnest-desktop 1>/dev/null 2>/dev/null)'")),
One click, and its on my screen.
Or ..
("Netscape afu@Rx", EXEC, "ssh -a -x -k -n -P -q -l afu
Rx netscape -display fubar:0
file:///home/afu/.netscape/bookmarks.html"),
Runs netscape on host rx puts it on screen fubar
( host rx has no screen or keyboard attached for 5 years)
These examples show a multitude of things, but notice
how command line strings become pretty clickety
buttons on a popup menu.
Raymond