The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron@ronnatalie.com (Ron Natalie)
Subject: [TUHS] SunOS vs Linux
Date: Sun, 8 Jan 2017 09:52:34 -0500	[thread overview]
Message-ID: <03f001d269be$d930ea50$8b92bef0$@ronnatalie.com> (raw)
In-Reply-To: <201701080610.v086AMr7084906@chez.mckusick.com>

> The lawyers came back and said that "giving away SunOS technology could
lead to a stockholder lawsuit concerning the giving away of stockholder
assets." End of discussion. We had to go with MACH.

Gosh, this strikes a nerve.    The engineers at our company all had access
to the license generator (which we wrote).   The thing had an easy way to
kick out a 30-day demo license, so we always used that.    When we got
bought by a publicly traded company, they determined that the license keys
were an essential stockholder asset and took the license generator away from
us.   We all just edited out the code that checked the license out of the
program.   In fact, I believe at least one major release went out with an
undocumented environment variable that disabled the licensing system which
probably was a much bigger risk to stockholder assets than letting the
engineers issue themselves demo licenses.



  reply	other threads:[~2017-01-08 14:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-08  6:10 Kirk McKusick
2017-01-08 14:52 ` Ron Natalie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-01-04 17:08 Clem Cole
2017-01-06  2:32 ` ron minnich
2017-01-06  3:56 ` Dan Cross
2017-01-06  3:58   ` Larry McVoy
2017-01-06 14:27   ` Clem Cole
2017-01-07  2:58     ` Greg 'groggy' Lehey
2017-01-07  3:09       ` Warner Losh
2017-01-07  3:13         ` Larry McVoy
2017-01-07  3:12       ` Larry McVoy
2017-01-08 16:28   ` Angus Robinson
2017-01-08 18:02     ` Kay Parker   
2017-01-08 20:51       ` Clem cole
2017-01-09  3:00         ` Greg 'groggy' Lehey
2017-01-09  6:32           ` Arno Griffioen
2017-01-09  8:27             ` Wesley Parish
2017-01-09 13:07             ` Joerg Schilling
2017-01-09 15:57             ` Clem Cole
2017-01-09 16:08               ` ron minnich
2017-01-09 17:40                 ` Dan Cross
2017-01-09 17:32               ` Rico Pajarola
2017-01-10 11:02                 ` Joerg Schilling
2017-01-08 22:52     ` Wesley Parish
2017-01-09 19:45   ` Jacob Goense

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='03f001d269be$d930ea50$8b92bef0$@ronnatalie.com' \
    --to=ron@ronnatalie.com \
    /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).