From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
Subject: [TUHS] TCP/IP implementations
Date: Tue, 5 Oct 04 15:40:41 GMT [thread overview]
Message-ID: <0410051540.AA09972@ivan.Harhan.ORG> (raw)
"=?ISO-8859-15?Q?Jos=E9?= R. Valverde" <jrvalverde at cnb.uam.es> wrote:
> 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=
> =20
> it for some time. My na=EFvete at the time prevented me from ordering it (t=
> hat
> and the availability of BSD sources).
Ultrix-32 sources can be found on ifctfvax.Harhan.ORG in
/pub/UNIX/thirdparty/Ultrix-32/sources available via anonymous FTP.
MS
next reply other threads:[~2004-10-05 15:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 15:40 Michael Sokolov [this message]
2004-10-06 4:23 ` [TUHS] research unix Tim Newsham
2004-10-06 7:06 ` Warren Toomey
2004-10-06 7:19 ` Wesley Parish
2004-10-06 9:26 ` [TUHS] TCP/IP implementations Jose R. Valverde
2004-10-06 15:19 ` Jochen Kunz
2004-10-24 20:17 ` Jose R. Valverde
-- strict thread matches above, loose matches on Subject: below --
2004-10-06 15:42 Michael Sokolov
2004-10-05 13:41 patv
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=0410051540.AA09972@ivan.Harhan.ORG \
--to=msokolov@ivan.harhan.org \
/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).