Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!rutgers!rochester!uhura.cc.rochester.edu!aisl
From: aisl@uhura.cc.rochester.edu (Lawrence Landry)
Newsgroups: comp.sys.next
Subject: Re: Next Bugs
Message-ID: <3138@ur-cc.UUCP>
Date: 26 Sep 89 13:13:12 GMT
References: <2420@ucsfcca.ucsf.edu>
Reply-To: aisl@uhura.cc.rochester.edu (Lawrence Landry)
Organization: University of Rochester
Lines: 31

In article <2420@ucsfcca.ucsf.edu> jst@cca.ucsf.edu.UUCP (Joe Stong) writes:
>I got private mail from Avadis Tevanian, who appears to be a software
>manager at NeXT.  As it was private, I will not include it, but I will
>mention the content:  It did NOT contain either helpful suggestions or
>sympathy about my situation in maintaining a NeXT box.  It merely
>re-iterated observations that I had already made, and told me what I CANNOT
>do with the NeXT box (namely remote system administration).  I'd much rather 
>be told what I *CAN* do to improve my situation.  I don't have much choice
>in doing remote system administration.
>

If you look at the big picture of what NeXT is attempting to do with their
operating system, you would realize that remote system administration over
a tty line is kind of ridiculous.  They are attempting to make system
administration a user friendly graphical interface so that you don't have to
be a UNIX guru to run your system.  Along with everyone else, I have been
frustrated from time to time because things are temporarily more clumsy than
they were with the old way of doing things.

I can sympathize with your problems but I agree with NeXT.  They have other
projects which will better serve more people than to add remote system
administration.

If you have a NeXT in your office, you can set up the machines that you 
administer so that you can run NetInfo, etc. from your MegaPixel display on
the remote machine ushing the rsh command.  This should solve most of your
problems (provided that you have a cube.)

-- 
Larry Landry
University of Rochester