The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: John Gilmore <gnu@toad.com>
To: Clem Cole <clemc@ccc.com>
Cc: tuhs <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Unix on DEC AlphaServer 4000
Date: Sat, 19 Sep 2020 12:42:39 -0700	[thread overview]
Message-ID: <32401.1600544559@hop.toad.com> (raw)
In-Reply-To: <CAC20D2O4Yb=CAER6OWg2MNbcXutCqT1PnvQQYqK+B-K2FaPFEg@mail.gmail.com>

Nelson H. F. Beebe <beebe@math.utah.edu> wrote:
> We ran DEC OSF/1 until the power supplies on our several Alpha systems
> died, but it had an annual license fee, and the O/S shutdown when the
> license expired.

Clem Cole <clemc@ccc.com> wrote:
> The issue is license managers as Nelson says, but Internet search is your
> friend *i.e.* different unlimited time styles license PAKs for Tru64 have
> been reported to have been seen in the wild, however YMMV.

License managers now count as DRM, under the Digital Millennium
Copyright Act (though no such laws had been passed when the license
managers were first created).  So: is it worth breaking the law in many
countries, to maintain a historical curiosity?

Personally, I would throw DRM-encrusted software, and the hardware that
is dependent on it, into the dustbin of history.  Its creators had fair
warning that they were making their products unusable after they stopped
caring to maintain them.  They didn't care about their place in history,
nor about their users.  They did it anyway, for short-term profit and to
harass those people foolish enough to be their customers.  Their memes
should not be passed to future generations.  As Sir Walter Scott
suggested in another context, they "doubly dying, shall go down, to the
vile dust, from whence [they] sprung, unwept, unhonour'd, and unsung".

	John
	

  reply	other threads:[~2020-09-19 19:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-19  3:26 Paul Riley
2020-09-19  4:19 ` Rico Pajarola
2020-09-19  4:26 ` Nelson H. F. Beebe
2020-09-19 17:45   ` Clem Cole
2020-09-19 19:42     ` John Gilmore [this message]
2020-09-19  4:27 ` Adam Thornton
2020-09-19  4:33 ` Jon Forrest
2020-09-19 21:56   ` David Arnold
2020-09-20  5:29 Rudi Blom

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=32401.1600544559@hop.toad.com \
    --to=gnu@toad.com \
    --cc=clemc@ccc.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).