From: "William H. Mitchell" <whm@msweng.com>
To: Computer Old Farts Followers <coff@tuhs.org>
Subject: [COFF] Re: [ih] Fwd: Some Berkeley Unix history - too many PHDs per packet
Date: Sun, 10 Mar 2024 11:02:44 -0700 [thread overview]
Message-ID: <452081E6-D3BA-4FA1-9615-90F5DDAF21CA@msweng.com> (raw)
In-Reply-To: <Ze0n0rnRZ2JzM9vJ@faui48e.informatik.uni-erlangen.de>
At the U of Arizona, university lawyers would staple a page on the BSD contract that, among other onerous things, required UCB to indemnify UA for all harms related to usage of the software. A no-go, of course. Dr. Pete Downey discovered that we could run licenses through Kitt Peak National Observatory, with offices on the UA campus. The KPNO lawyer had the mindset of helping researchers do research, and our licensing problems were solved. :)
--whm
next prev parent reply other threads:[~2024-03-10 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <606871377.2352922.1709955781555@mail.yahoo.com>
[not found] ` <84A5C4DC-E9E7-46F7-AA6C-AADD64ACD305@icloud.com>
2024-03-09 19:52 ` Clem Cole
2024-03-10 3:24 ` Toerless Eckert
2024-03-10 18:02 ` William H. Mitchell [this message]
2024-03-10 10:05 ` steve jenkin
2024-03-10 19:58 ` Clem Cole
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=452081E6-D3BA-4FA1-9615-90F5DDAF21CA@msweng.com \
--to=whm@msweng.com \
--cc=coff@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).