The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Josh Good <pepe@naleco.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Micnet Was: Re: Surprised about Unix System V in the 80's - so sparse!
Date: Sat, 20 Mar 2021 12:50:19 +0100	[thread overview]
Message-ID: <20210320115018.GA9713@naleco.com> (raw)
In-Reply-To: <F4655783-100E-44A8-8EFD-37F3BBA9335C@blat.at>

On 2021 Mar 18, 12:27, Mike Knell via TUHS wrote:
> 
> > 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.

This SCO technical article explains in detail how to set up Micnet
networking on SCO Unix.

https://www.scosales.com/ta/kb/103649.htmlOB

Amusingly, the article says "The System Administrator's Guide for older
versions of SCO UNIX System V/386 contained a section on the Micnet network,
but this is not present in the SCO UNIX System V Release 3.2 Version 4.0
documentation. The documentation for this network is provided here.  Users
who wish to use this network system will require this documentation."

So it seems by the early 90's SCO was indeed phasing out the old Xenix
Micnet networking scheme.

Reading that article is interesting, and Micnet seems to have been a fragile
concoction. The article even says at the end: "You can only use mail to
transfer small files.  Large files are randomly truncated by mail." Not the
most reassuring thing to read about the computer system you are using...

-- 
Josh Good


  parent reply	other threads:[~2021-03-20 12:11 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
2021-03-20 11:50   ` Josh Good [this message]
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=20210320115018.GA9713@naleco.com \
    --to=pepe@naleco.com \
    --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).