🚀 go-pugleaf

In article <hendersoDoxuAu.7uv@netcom.com>,
Mark C. Henderson <henderso@netcom.com> wrote:
 >In article <4jbpkj$eo5@clark.net>, Marcus J. Ranum <mjr@clark.net> wrote:
 >>Larry Motylinski <larry@pronet.mpro.net> wrote:
 >>	And if the system is a hospital's database, or something
 >>mission critical and life-threatening, and they change their
 >>hardware, you'll get a call from their lawyers if it was your
 >>stupid copy protect that caused downtime. Think carefully before
 >>you do something that will put your customers out of business
 >>as a means of protecting your software against them!
 >
 >As a systems administrator for company with a lot of software which 
 >is node locked (or where the licence servers are node locked), having 
 >software and/or techniques for keeping mission critical software 
 >running temporarily in the event of a hardware change is an essential 
 >part of a disaster recovery plan. 

How about not putting any stupid funny business into the software? What a novel
idea that is. Or maybe even selling the poor users a source code
license! Imagine that...

Viewing a customer as a hostile turns him into an enemy.

--