HP3000-L Archives

February 1995, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Kell <[log in to unmask]>
Reply To:
Jeff Kell <[log in to unmask]>
Date:
Sun, 5 Feb 1995 19:01:12 EST
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
On Sat, 4 Feb 1995 17:19:35 -0500 Daniel Kosack said:
>  Well, TCP/IP and Internet stuff in general in not 'impossible' per se
>on the HP 3000, just maybe the toughest thing you may ever try to do.
>Last year I tried to get an Internet connection going on a MPE V system.
>[snip]... But, even though you may be able to send/recieve TCP/IP
>packets, it's doubtless that you have the daemons for all of the Internet
>apps, such as telnet, snmp, etc.
 
And in a later posting Daniel Kosack said:
  From what I've seen, porting UNIX to MPE (at least elder MPE versions)
is pretty close to impossible.  I haven't heard of anything being
successfully ported without major overhaul. Heh we're even talking about
going through and changing file naming schemes, not to mention lib calls.
 
MPE/iX has been very network friendly since 4.0 when external DNS servers
were supported.  Prior to that, you could get decent TCP/IP connectivity
if you maintained your own host directories, even back on MPE/V.
 
As of 5.0, all you need is an external DNS server and you are ready to go
with Berkeley sockets, FTP, outbound telnet, ping, SNMP, etc.  Third-party
packages provide SMTP, NFS, LPR, and LPD (among others).  In spite of it's
tainted past, the 3000 is now readily networkable in a TCP/IP (Internet)
environment.
 
[\] Jeff Kell, [log in to unmask]

ATOM RSS1 RSS2