LAT Terminal Server Manager for Ultrix

[George Robbins]

In article <4169 at shlump.nac.dec.com> michaud at decvax.dec.com (Jeff Michaud) writes:
> In article <7683 at cbmvax.UUCP>, grr at cbmvax.UUCP (George Robbins) writes:
> > ..., which, like DECnet, is sort of grafted onto the Unix networking
> > while remaining it's own rather perverse view of the world...

> DECnet is not "grafted" onto Unix networking.  We use the same device drivers
> as IP.  We are no more "grafted" on than IP, just that we aren't bundled with
> the base system

Maybe we can agree to disagree or disagree to agree or simply become confused...

By grafted, I mean that they did share the same "roots", the "network" device
drivers.  I don't have any real problem with this.  On the other hand, much
of DECnet seems to me like an pear branch on an apple tree, some "generic DEC"
code that happens to run under Unix.  The ncp(8) program and the Decnet
"configuration" databasese aren't exactly in the unix idiom and can be quite
excruciating, especially when ncp starts returning cryptic error messages or
when you've let it interactivly guide you thru entering a command and then
you get a "syntax error" type message.  It would be nice if it knew about
the same "device names" as everybody else, too.

By the way, now that we have all this nice "generic file system" stuff,
why can't ultrix use the DECnet protocols for remote file access?  In the
long run, NFS servers running under VMS would seem more efficient, but
for "convenience" purposes, the DECnet mode would be nice.  If I can access
Ultrix files directly from VMS via DECnet, I out to be able to go the
other way, without having to resort to command line style copy programs...

-- 
George Robbins - now working for,	uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr at uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)