From: Clem Cole <clemc@ccc.com>
To: arnold@skeeve.com
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Unix, IBM, 370
Date: Tue, 5 Nov 2019 09:15:35 -0500 [thread overview]
Message-ID: <CAC20D2Nn4hEL4gMOcg4LFfADaErkRaF2Zir_=3H_rdGeXVZZig@mail.gmail.com> (raw)
In-Reply-To: <201911041443.xA4EhCqn023852@freefriends.org>
[-- Attachment #1: Type: text/plain, Size: 1394 bytes --]
IBM owned TCF and it was 100% screwed down into AIX. The clean room team
which did TNC used many of the ideas but tried to make it layered into 14
separate technologies so customer could pick and choose. HP originally
picked up the process technology but not the FS work. DEC was the
reverse. Novell/Tandem took all it. HP ended up with all the IP and in
the end released it as FOSS. Hence the OpenSSI project
On Mon, Nov 4, 2019 at 9:43 AM <arnold@skeeve.com> wrote:
> Clem Cole <clemc@ccc.com> wrote:
>
> > On Sun, Nov 3, 2019 at 12:06 AM <arnold@skeeve.com> wrote:
> >
> > >
> > > > The ideas were recreated as 14 different technologies called
> Transparent
> > > > Network Computing (TNC) that would end up in the FOSS community and
> added
> > > > to Linux 2x kernel as: OpenSSI <
> https://en.wikipedia.org/wiki/OpenSSI>
> > >
> > > Am I wrong, or does nobody actually use this today? The opessi.org
> > > home page link from Wikipedia just seems to hang. And the files on the
> > > SourceForge page are 5 years old.
> > >
> > I suspect not - it was done to 2.6 kernel and none of the changes were
> > taken by Linus for 3x Folks got discouraged and gave up
>
> Ah, OK. Thanks for the info. On the one hand, two bad. On the other hand,
> it looks like a real patchwork quilt of technologies...
>
> Thanks,
>
> Arnold
>
--
Sent from a handheld expect more typos than usual
[-- Attachment #2: Type: text/html, Size: 2173 bytes --]
next prev parent reply other threads:[~2019-11-05 14:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 4:04 Warren Toomey
2019-10-29 5:07 ` Warner Losh
2019-10-29 5:19 ` Adam Thornton
2019-10-29 7:14 ` SPC
2019-10-29 15:10 ` Warner Losh
2019-10-29 15:22 ` SPC
2019-11-05 4:12 ` Grant Taylor via TUHS
2019-10-31 3:56 ` Tom Lyon
2019-10-31 4:16 ` Larry McVoy
2019-10-31 7:51 ` arnold
2019-10-31 13:51 ` Tom Lyon
2019-10-31 14:10 ` arnold
2019-10-31 14:22 ` Larry McVoy
2019-10-31 14:24 ` SPC
2019-10-31 15:31 ` Charles H Sauer
2019-11-01 16:52 ` Clem Cole
2019-11-03 7:05 ` arnold
2019-11-03 21:16 ` Clem Cole
2019-11-04 14:43 ` arnold
2019-11-05 14:15 ` Clem Cole [this message]
2019-10-31 15:10 ` Heinz Lycklama
2019-11-01 16:40 ` Clem Cole
2019-10-31 8:09 ` SPC
2019-10-31 15:12 ` Warner Losh
2019-11-03 1:02 ` Kevin Bowling
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='CAC20D2Nn4hEL4gMOcg4LFfADaErkRaF2Zir_=3H_rdGeXVZZig@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=arnold@skeeve.com \
--cc=tuhs@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).