The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Wesley Parish <wobblygong@gmail.com>
To: Jason Stevens <jsteve@superglobalmegacorp.com>
Cc: "tuhs@minnie.tuhs.org" <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] ISO, OSI, and DECnet (was Re: If not Linux, then what?)
Date: Fri, 30 Aug 2019 21:32:21 +1200	[thread overview]
Message-ID: <CACNPpea_Vj5dYf3yzTPZT4jYBBgscVd1QD7TELeTD8DskugAzw@mail.gmail.com> (raw)
In-Reply-To: <1d3d8c9a-7006-4666-b32e-8fa4fc5e9f7c@PU1APC01FT039.eop-APC01.prod.protection.outlook.com>

Well, fwiw, the Aeronautical Telecommunications Network (ATN) that was
being discussed in the late nineties and early noughties, was supposed
to be built on the OSI stack. I have no idea what happened with that,
whether it went ahead or got altered.

On 8/30/19, Jason Stevens <jsteve@superglobalmegacorp.com> wrote:
> Although I never have seen OSI in the wild, it was the one great thing about
> ‘Winsock’ is that it worked over TCP/IP , IPX/SPX, AppletTalk and Decnet.
> It was fun to convert a BBS from being telnet to some ‘telnet over decnet’
> monster I built.
>
> Although I’m guessing OSI would have allowed for common ‘network’
> applications to use different network topologies?
>
> I really need to get OSF/1 2.0 installed.
<snip>

  reply	other threads:[~2019-08-30  9:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28 16:50 Paul Winalski
2019-08-28 17:24 ` Larry McVoy
2019-08-28 17:45   ` Jon Forrest
2019-08-28 17:50     ` Larry McVoy
2019-08-28 18:17   ` Kurt H Maier
2019-08-28 19:29     ` SPC
2019-08-29  0:29       ` George Michaelson
2019-08-29 14:54       ` Jason Stevens
2019-08-30  9:32         ` Wesley Parish [this message]
2019-08-30 13:59           ` Clem Cole
2019-08-31 23:38         ` Grant Taylor via TUHS

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=CACNPpea_Vj5dYf3yzTPZT4jYBBgscVd1QD7TELeTD8DskugAzw@mail.gmail.com \
    --to=wobblygong@gmail.com \
    --cc=jsteve@superglobalmegacorp.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).