From: patv@monmouth.com (patv@monmouth.com)
Subject: [TUHS] TCP/IP implementations
Date: Tue, 5 Oct 2004 08:41:22 EST [thread overview]
Message-ID: <200410051341.i95DfMOW016600@wwws.monmouth.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2292 bytes --]
It's not a question of it being lost, but rather making sure it doesn't
become lost. My first order of business is for the product that was the
reason for Manalapan's existence -- VAX System V.
The Manalapan, NJ site, after two mergers, is still today known as UNX
because of it initial charter to port AT&T Unix to VAX. This dates back
to the old DEC days where all sites had a 3 character identifier. I guess
someone was a private pilot and modeled it after airport designations.
Anyway, Manalapan was also frequently used as a hub in a lot of uucp
activity -- just look for UNXA in the path.
Enough history for today.
Pat
> On Fri, 01 Oct 2004 06:09:19 -0400
> Pat Villani <patv at monmouth.com> wrote:
> > Don't know about a TCP/IP stack, but I'm sorry to tell you that Ultrix
> > is still proprietary and now owned by hp.
> >
> > The source is in danger of being lost unless I'm successful over the
> > next six months. The Manalapan, NJ site where a great deal of Ultrix
> > work was done will be closing soon and employees moved to other
location>
> > and otherwise. I volunteered to take the old tape archives and
transfer>
> > the source code to CD-ROM for preservation. I don't know if there are
> > any other copies in Nashua, NH, where the remainder of the work was done.
> >
> > Pat
> >
> While working at the Biomedical Research Institute (Madrid, Spain) I got a
> quote from DEC for access to Ultrix source code. As I remember it, it wasn't
> that expensive (~1000$ for an academic license) and I mused bout
acquiring>
> it for some time. My na�vete at the time prevented me from ordering it
(t> hat
> and the availability of BSD sources).
>
> But I'd feel pretty sure that at that price many source licenses must have
> been sold. Maybe there are still copies lying around and you can find
> someone to send you a copy back.
>
> Sure, it would be nicer to maintain the whole development log and versions.
>
> j
> --
> These opinions are mine and only mine. Hey man, I saw them first!
>
> Jos� R. Valverde
>
> De nada sirve la Inteligencia Artificial cuando falta la Natural
>
---------------------------------------------
This message was sent using Monmouth Internet MI-Webmail.
http://www.monmouth.com/
next reply other threads:[~2004-10-05 13:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 13:41 patv [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-06 15:42 Michael Sokolov
2004-10-05 15:40 Michael Sokolov
2004-10-06 9:26 ` Jose R. Valverde
2004-10-06 15:19 ` Jochen Kunz
2004-10-24 20:17 ` Jose R. Valverde
2004-10-01 5:14 Sergey Lapin
2004-10-01 10:09 ` Pat Villani
2004-10-05 13:03 ` José R. Valverde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200410051341.i95DfMOW016600@wwws.monmouth.com \
--to=patv@monmouth.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).