The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Rich Morin <rdm@cfcl.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Prime Time Freeware <- Sun User Group tapes
Date: Tue, 16 Feb 2021 13:12:35 -0800	[thread overview]
Message-ID: <CF71381E-7421-4D0F-B317-157B64F2839C@cfcl.com> (raw)
In-Reply-To: <30266.1613504349@hop.toad.com>

> On Feb 16, 2021, at 11:39, John Gilmore <gnu@toad.com> wrote:
> 
> ... A copy of both the 1987 tape and the 1989 tape are here:
> 
>  http://www.toad.com/SunUserGroupTape-Rel-1987.1.0.tar.gz
>  http://www.toad.com/SunUserGroupTape-Rel-1989.tar
>  http://www.toad.com/

As always, John Gilmore rocks...  (John, can you tell folks about the
history, rationale, and text of the Sun-1's PROM identification message?)

> I'll have to do a bit more digging to turn up more than vague memories
> about our dealings with the lawyers...

I have two legal war stories to relate, offhand...

# AT&T

I tried to find a way to get permission to include copies of text files
(both vanilla and modified, IIRC) that were part of the "binary" release.
(I thought it might be useful for folks to have backup and/or "improved"
versions.)  I was flatly informed that all files in a binary distribution
were, by definition, binary (not text).  So, we had nothing to discuss.
I never did manage to break through that legal stonewall.

# Sun

The other story (fortunately!) ended more successfully.  You see, Sun's
legal staff had drafted a "minimal" agreement that folks _donating_ bits
were expected to sign off on.  IIRC, it ran on for about twenty pages (!).

John and I were both appalled and tried to tell the lawyer we met with that
the authors and organizations involved wouldn't sign off on anything like
this; indeed, they wouldn't even read it.

Since John was pretty incensed, I got to play Good Cop.  IIRC, I asked John
to list the issues that he thought reasonable for the agreement to cover.
With some grumbling, he came up with a set of issues whose legalese filled
one side of a (letter-size :-) page.

I then turned to the Sun lawyer (who was actually trying to be helpful and
make things work) and asked him to tell us about any _critical_ issues John
had left out.  However, I only gave him a one-page budget.

Adding the mutually acceptable issues brought the agreement up to two pages,
which I got John (with a bit more grumbling) to accept.  The lawyer then
had the (unenviable) task of getting Sun to sign off on it.  He did, and SUG
was able to get donation sign-offs and produce a useful tape (whew!).  I'm
sure it helped that the folks doing the first tape were working at LLNL...

-r




      reply	other threads:[~2021-02-16 21:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-14 21:05 [TUHS] Prime Time Freeware Chris Hanson
2021-02-14 22:04 ` Nemo Nusquam
2021-02-15  0:17   ` Kenneth Goodwin
2021-02-15 23:32   ` Chris Hanson
2021-02-16  2:28 ` Derrik Walker v2.0
     [not found]   ` <7193CD22-B517-41AA-BE0F-3BAFBAD52A62@cfcl.com>
2021-02-16 19:39     ` [TUHS] Prime Time Freeware <- Sun User Group tapes John Gilmore
2021-02-16 21:12       ` Rich Morin [this message]

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=CF71381E-7421-4D0F-B317-157B64F2839C@cfcl.com \
    --to=rdm@cfcl.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).