From: Jim Capp <jcapp@anteil.com>
To: Mike Knell <m@blat.at>
Cc: TUHS main list <tuhs@minnie.tuhs.org>, Paul Ruizendaal <pnr@planet.nl>
Subject: Re: [TUHS] Micnet Was: Re: Surprised about Unix System V in the 80's - so sparse!
Date: Thu, 18 Mar 2021 07:04:48 -0500 (EST) [thread overview]
Message-ID: <22485620.13.1616069088201.JavaMail.root@zimbraanteil> (raw)
In-Reply-To: <F4655783-100E-44A8-8EFD-37F3BBA9335C@blat.at>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
Yes, we used MMDF quite extensively until TCP/IP.
I remember paying $800 for a network card for a PC in the mid 90's.
Just this week, I discarded a box filled with old 10/100 cards.
From: "Mike Knell via TUHS" <tuhs@minnie.tuhs.org>
To: "Paul Ruizendaal" <pnr@planet.nl>
Cc: "TUHS main list" <tuhs@minnie.tuhs.org>
Sent: Thursday, March 18, 2021 7:27:26 AM
Subject: Re: [TUHS] Micnet Was: Re: Surprised about Unix System V in the 80's - so sparse!
> On 18 Mar 2021, at 10:44, Paul Ruizendaal via TUHS <tuhs@minnie.tuhs.org> wrote:
>
> Does anybody here know the backstory to Micnet and/or how it worked?
The Xenix communications manual has plenty of detail on how to set it up:
http://www.nj7p.org/Manuals/PDFs/Intel/174461-001.pdf
Looks as if it built a routed network among a set of Xenix machines using
conventional serial lines, including remote login / file transfer / mail
ervices. Would have been quite a big selling point for software development
shops in the days before TCP/IP and ubiquitous connectivity, especially as
it looks as if it was decentralised and didn’t require any extra server
hardware. MMDF could route mail between Micnet and UUCP.
Mike
[-- Attachment #2: Type: text/html, Size: 1572 bytes --]
next prev parent reply other threads:[~2021-03-18 12:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 9:44 Paul Ruizendaal via TUHS
2021-03-18 11:27 ` Mike Knell via TUHS
2021-03-18 12:04 ` Jim Capp [this message]
2021-03-20 11:50 ` Josh Good
2021-03-20 15:16 ` Larry McVoy
2021-03-21 0:08 ` Wesley Parish
2021-03-21 0:18 ` Larry McVoy
2021-03-21 1:12 ` Greg 'groggy' Lehey
2021-03-21 1:31 ` Larry McVoy
2021-03-21 1:42 ` Kevin Bowling
2021-03-21 2:38 ` [TUHS] SCO marketing FreeBSD (was: Micnet, Was: Surprised about Unix System V in the 80's - so sparse!) Greg 'groggy' Lehey
2021-03-21 2:43 ` Kevin Bowling
2021-03-21 3:02 ` Warner Losh
2021-03-21 3:04 ` Greg 'groggy' Lehey
2021-03-21 3:09 ` Warner Losh
2021-03-21 6:53 ` Dave Horsfall
2021-03-21 11:01 ` Harald Arnesen
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=22485620.13.1616069088201.JavaMail.root@zimbraanteil \
--to=jcapp@anteil.com \
--cc=m@blat.at \
--cc=pnr@planet.nl \
--cc=tuhs@minnie.tuhs.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).