9 Sep
2003
9 Sep
'03
7:40 a.m.
On 9/6/2003 08:45 PM -0500, cctech-request(a)classiccmp.org wrote:
From: "Antonio Carlini"
<arcarlini(a)iee.org>
Subject: RE: DEC Server
Date: Thu, 4 Sep 2003 18:13:06 +0100
Yes, that is correct. The Pluto was originally targeted to be the terminal
front-end running CTERM for the Jupiter.... but that didn't happen.
LAT was prototyped on one of those VT100s with an LSI-11 in it.
No reason for a correction: it was indeed DECnet
and LAT
BTW: Someone else said that DS100 was the DEC first terminal
server. But the DECSA (PDP-11/24 based) preceded it. (I think
that was code named Pluto; if it wasn't, then there must have
been an even earlier one). ...
Incorrect. Sort of like saying DHCP is not part of the TCP/IP stack,
because it doesn't run UDP frames.
MOP is the the Maintance Operations Protocol of the DECnet
architecture. If you can find the spec (DECnet specs were published), it
will say DECnet on it.
(I have one in box somewhere)
For that matter, LAT, while not developed as part of the traditional DECnet
protocol set, but it was sold as a Digital networking product. A marketer
would consider LAT part of the "DECnet" product set. (though it was a pure
LAN protocol that was proprietary, private, and licensed - all things not
done with other DECnet protocols.)
Dave.
DECnet (MOP, to be more precise) was used for
software download and
from terminal ports to hosts on the net). LAT is *not* part of DECnet
(which is often claimed), it's a separate protocol. However, it was
common to run LAT on a host that also would run DECnet.
MOP isn't part of DECnet either.