Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!gatech!emory!stiatl!todd
From: todd@stiatl.UUCP (Todd Merriman)
Newsgroups: comp.unix.questions
Subject: Re: VMS -> Ultrix transition
Message-ID: <4539@stiatl.UUCP>
Date: 4 May 89 16:45:19 GMT
References: <19412@adm.BRL.MIL>
Reply-To: todd@stiatl.UUCP (Todd Merriman)
Organization: Sales Technologies Inc., a teeny little company in the existance of creation...
Lines: 23

In article <19412@adm.BRL.MIL> sbbur%CONNCOLL.BITNET@cunyvm.cuny.edu writes:
>I'm looking for suggestions on making the transition from VMS to Ultrix
>easier for our users.........

As a developer spending nearly equal time on both SysV and VMS,
I highly recommend *NOT* trying to emulate DCL on the Ultrix
system.  Please understand that I have no interest in comparing
DCL versus the Shell.  What I feel is important is to use the
command processor best suited to the o/s.  If you emulate DCL in
the Ultrix environment, your users will never learn to use the
Shell; and, the Shell is far better suited to exploit the strengths
of Unix.

If your users are used to EDT, VI is functionally equivalent.
More powerful editors are available from third-parties, but
will require a learning curve.  I learned EDT so that I could
edit on *any* VAX running VMS.  I learned VI so that I could edit
on any SysV.  Neither editor is even in the same ballpark as
BRIEF, which I use on my PC to do the majority of my program
editing.

   ...!gatech!stiatl!todd
   Todd Merriman * 404-377-TOFU * Atlanta, GA