The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: John Gilmore <gnu@toad.com>
Cc: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: Re: [TUHS] Troff to ps
Date: Thu, 28 Jan 2021 07:58:56 -0500	[thread overview]
Message-ID: <CAC20D2M0ieG1_U7W5tMS3Rjd7SoTQV-SO8Rr04pOuJ08X0zU9Q@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2NCJEhfB5NgaigE8URTKuCqjUtr4nxtrnm4P9Fg3YQ2fA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2464 bytes --]

Ditroff per cpu was cheap. I was part of all those negotiation.    There
was a buy in that way high and John points out.  Actually there were two -
one to get the sources for your first internal cpu and another for the
redistribution rights.

My memory of the first license for the original ditroff 1.0 typesetter was
5k (which included the new C compiler) although it did drop later when it
went into the toolchest.  But There was also redistribution fee also which
iirc you worked off / creditted against like license fees.

The entire v7 OS redistribution fee was on the 50-100k range (I've
forgotten but am likely to have that in my att files somewhete) - which was
after the 25k single cpu source license. The original binary per cpu
redistribution license started at 1.5k.  Which when a minicomputer was
selling at 150k was not terrible.  The problem was a PC at 5k.

I was in the room at Riki's Hyatt in Palo Alti when that was all
negotiated.  This would lead to the Sys III license. It was at that MTG
Gates famous looked at the rest of us and said "you guys don't get it.  The
only thing that matters is volume".  He wanted to pay $50/copy max.

Anyway troff was much cheaper than the whole OS license.   The per cpu
charge was very small as I said my memory is it was $5 over the base OS
license.

On Wed, Jan 27, 2021 at 8:25 PM Clem Cole <clemc@ccc.com> wrote:

> Actually  It was very cheap. $5 a copy if I remember correctly   Masscomp
> and Stellar just ate the cost.  The adobe transcript license was also
> nominal.  In both cases we realized it was cheaper than trying to keep two
> separate streams and figure out which systems we shipped it too.
>
> On Wed, Jan 27, 2021 at 7:26 PM John Gilmore <gnu@toad.com> wrote:
>
>> Greg A. Woods <woods@robohack.ca> wrote:
>> > As I recall even some of the bigger vendors such as Sun and IBM didn't
>> > offer ditroff in their base OS, but they did offer old troff.  Those
>> > were the days of insane AT&T licensing and all the games competitors
>> > played around it.
>>
>> As I recall, AT&T wanted about the same amount of money for ditroff as
>> for the entire UNIX release.  So, of course no UNIX vendor was going to
>> double the royalty they paid to AT&T for every customer, for a small
>> improvement in a utility that most customers didn't even use (troff).
>>
>>         John
>>
>> --
> Sent from a handheld expect more typos than usual
>
-- 
Sent from a handheld expect more typos than usual

[-- Attachment #2: Type: text/html, Size: 3489 bytes --]

  parent reply	other threads:[~2021-01-28 12:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-26 14:56 Will Senn
2020-07-26 15:31 ` arnold
2020-07-26 15:35   ` arnold
2020-07-26 16:15     ` Clem Cole
2020-07-26 17:11       ` arnold
2020-07-26 18:03         ` Clem Cole
2021-01-27  5:24           ` Greg A. Woods
2021-01-28  0:19             ` John Gilmore
2021-01-28  1:25               ` Clem Cole
2021-01-28  1:59                 ` Larry McVoy
2021-01-28  3:19                 ` John Gilmore
2021-01-28 12:58                 ` Clem Cole [this message]
2020-07-26 19:05   ` Nemo Nusquam
2020-07-26 22:39     ` Noel Hunt
2020-07-27  5:31     ` arnold
2020-07-27  9:19       ` Jaap Akkerhuis
2020-07-27 11:07         ` Brad Spencer
2020-07-27 15:58   ` Will Senn
2020-07-26 15:33 ` Clem Cole
2020-07-27 15:53   ` Will Senn
2020-07-26 18:09 ` Al Kossow
2020-07-26 23:37 Norman Wilson
2020-07-27 15:08 ` Jaap Akkerhuis
2020-07-28 11:33 Doug McIlroy

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=CAC20D2M0ieG1_U7W5tMS3Rjd7SoTQV-SO8Rr04pOuJ08X0zU9Q@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=gnu@toad.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).