Path: utzoo!utgpu!watmath!clyde!att!rutgers!ucsd!ucbvax!H.GP.CS.CMU.EDU!Rudy.Nedved
From: Rudy.Nedved@H.GP.CS.CMU.EDU
Newsgroups: comp.protocols.tcp-ip
Subject: Re: CMU-TEK tcp/ip and 'C'
Message-ID: <8811260827.AA06003@ucbvax.Berkeley.EDU>
Date: 26 Nov 88 06:18:05 GMT
References: <8811241840.AA06288@quiche.cs.mcgill.ca>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 19


There is already a mailing list for discussing CMU Tektronix TCP/IP. The
address is CMU-TEK-TCP@CS.CMU.EDU and to be added to the list you send
mail to CMU-TEK-TCP-REQUEST@CS.CMU.EDU.

You will find that there are alot of little problems that you will encountered
with the very insecure rsh, rlogin and rexec system that Berkeley hacked up.
   - you will be giving your VMS machine more access power to your Unix
     machines (possibly giving any VMS user access to root on your Unix
     machines).
   - you will have to fight with the conflicts from standard TCP/IP not having
     the insecure "priviledged" port concept Berkeley Unix has. Forcing the
     VMS application to allocate a number less then 512 will be tough. Making
     VMS/Unix communication reliable when reusing a port-pair that was just
     used in the last 2 minutes will be tough.
   - mapping Unix semantics to and from VMS semantics for interrupts and
     for terminal i/o will be trickier then telnet...

-Rudy