The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Ruizendaal via TUHS <tuhs@minnie.tuhs.org>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: [TUHS] Micnet Was: Re: Surprised about Unix System V in the 80's - so sparse!
Date: Thu, 18 Mar 2021 10:44:04 +0100	[thread overview]
Message-ID: <F49841E3-F62F-499B-A7AA-D1B4B8EA1AD1@planet.nl> (raw)


Micnet would seem to fall within my interest scope of Unix networking 1975-1985. I’ve seen it mentioned before, but I don’t have a clear picture of what it was.

There is some sysadmin material on bitsavers about it, but no info on how it worked on the inside or how it relates to other early networking.

At first glance it seems to be conceptually related to Berknet.

Does anybody here know the backstory to Micnet and/or how it worked?

Paul


             reply	other threads:[~2021-03-18  9:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18  9:44 Paul Ruizendaal via TUHS [this message]
2021-03-18 11:27 ` Mike Knell via TUHS
2021-03-18 12:04   ` Jim Capp
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=F49841E3-F62F-499B-A7AA-D1B4B8EA1AD1@planet.nl \
    --to=tuhs@minnie.tuhs.org \
    --cc=pnr@planet.nl \
    /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).