The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: George Michaelson <ggm@algebras.org>
To: tuhs@tuhs.org
Subject: [TUHS] Re: UNIX on (not quite bare) System/370
Date: Tue, 20 Dec 2022 11:57:49 +1000	[thread overview]
Message-ID: <CAKr6gn1TJd6rMG8Ys+cC2EtW1aCEpQeS8GyZBH-8bGec8TU7=w@mail.gmail.com> (raw)
In-Reply-To: <20221220013323.GL4401@mcvoy.com>

Any comment now about taking ideas from Berkeley is informed by the
twisted history which followed. At the time I can totally understand a
preference for code from the tertiary education sector over IBM absent
some explicit decision higher up about IPR: dealing with IBM must have
been a very complicated story for Bell over time, and it wasn't that
long since the whole CP/M MS-DOS thing had blown up with sillyness on
both sides. It is entirely possible a decision with this much weight
was made on a hunch/feel at some desk who had suffered at the hands of
big blue lawyers at the time. Just because at a transatlantic distance
I found the regents a nightmare to deal with (4.1 to 4.2 upgrade,
re-licencing with bodies moving so signatures differing, then much
later the same dance over some VLSI design s/w at UQ in Australia)
doesn't mean Bell would have. To the contrary, they might have had the
lowest bar legal and contractual barriers to work with.

There was also the whole thing about DoD funding. Sockets are crap. I
think they only became a de-facto standard because of familiarity. But
again, put that back into historical context and have a platform
coming out of the Californian state education system funded by the DoD
with a network interface. DoD funding..yea lets hitch on that: maybe
there will be some more of that sweet DARPA money flowing and if we're
familiar with it, then we can get into the future contracts: Not that
anyone cutting code thinks that way but desk jockeys would maybe?

York Unix was how I met things on a Vax with VM. I remain a fan of how
Charles Forsyth codes things. Small and elegant. I don't know that it
fed back into anything.

  reply	other threads:[~2022-12-20  1:59 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 17:38 [TUHS] " Phil Budne
2022-12-19 18:53 ` [TUHS] " segaloco via TUHS
2022-12-19 21:01   ` Clem Cole
2022-12-19 21:19     ` Rob Pike
2022-12-19 22:15       ` segaloco via TUHS
2022-12-20  0:02         ` Brad Spencer
2022-12-20  1:04           ` Adam Thornton
2022-12-20  2:35             ` segaloco via TUHS
2022-12-20 14:25           ` Andrew Hume
2022-12-19 23:02       ` Clem Cole
2022-12-20  1:20         ` Larry Stewart
2022-12-20  1:33           ` Larry McVoy
2022-12-20  1:57             ` George Michaelson [this message]
2022-12-20  2:06               ` Dan Cross
2022-12-20 15:04                 ` Chet Ramey
2022-12-20  2:12               ` Adam Thornton
2022-12-20 15:29                 ` Andy Kosela
2022-12-20 15:35                   ` Adam Thornton
2022-12-21  2:43                     ` Luther Johnson
2022-12-20 23:18                 ` David Arnold
2022-12-20  2:52       ` Bakul Shah
2022-12-20  3:09         ` Larry McVoy
2022-12-20  3:27           ` Bakul Shah
2022-12-20  3:48           ` Warner Losh
2022-12-20  4:21           ` Jonathan Gray
2022-12-19 21:36 ` Marc Donner
2022-12-19 22:52   ` Charles H Sauer (he/him)
     [not found]   ` <01428a75-3507-7b8a-fd35-cef74c8c0bd2@ucsb.edu>
2022-12-20  1:49     ` [TUHS] Re: pre-1991 USENIX proceedings Marc Donner
2022-12-20  3:11 ` [TUHS] Re: UNIX on (not quite bare) System/370 Warner Losh
2022-12-20  8:56 ` arnold
2022-12-20  9:31   ` segaloco via TUHS
2022-12-20  9:39     ` arnold
2022-12-20  9:55       ` Jonathan Gray
2022-12-20 14:27     ` Clem Cole
2022-12-23  1:53       ` Rob Gingell
2022-12-22 19:00 ` Andrew Hume
2022-12-20 22:25 Noel Chiappa
2022-12-20 23:18 ` Bakul Shah
2022-12-22 17:26 Noel Chiappa
2022-12-22 17:33 ` Dan Cross
2022-12-22 20:25 ` Warner Losh
2022-12-22 23:06   ` Warner Losh

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='CAKr6gn1TJd6rMG8Ys+cC2EtW1aCEpQeS8GyZBH-8bGec8TU7=w@mail.gmail.com' \
    --to=ggm@algebras.org \
    --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).