🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: vmsnet.internals
1 messages
1 total messages Started by Ehud Gavron 602-570-2546 Wed, 27 Jan 1993 00:11
Re: How to force a process into one CPU on a 6640?
#519
Author: Ehud Gavron 602-570-2546
Date: Wed, 27 Jan 1993 00:11
53 lines
2603 bytes
Date sent:  26-JAN-1993 17:07:03

Tom Otoole commented:
>
>I'm curious if anyone has explored the license implications of this. By way of
>concrete example, suppose Wingra Inc. wants to squeeze 3000$ out of me, plus an
>extra 450$/yr. maintenance, because I add another CPU to a 6400 box. In a way
>it seems reasonable that if I bind the software to one CPU, that I am still in
>keeping with my original single CPU license.

Putting on my hacker hat:
        I can create any license for any product, or get around
        any vendor's schemes to prevent me from running the software.

Putting on my user's hat:
        Why do they charge me #*$)*)#$ much to run the SAME #&*(#$
        thing on my 6640 instead of the piddly amount they charge
        me to run it on my 2000???  It makes no sense!

Putting on my developer's hat:
        Really if someone uses my product, I'd like to charge them
        more if it's used more.  I figure on a 6640 they'll get
        more than two orders of magnitured more transactions in
        a year than they will on my VAX 11/725.  However, there's
        no reasonable way to account for how many transactions
        they really will do.  Plus, if the number turned out small,
        they might cancel... so...

        *blink*

        Idea!  We'll charge by CPU size, regardless of how much
        they really run the product!

Answer: Your particular license covers the machine you run the software
        on, NOT the possible configuration your machine COULD have if
        you (effectively) disable a CPU or two or three.  Thusly, you
        buy licenses based on the hardware.

Putting on my legal hat:
        I am not a lawywer, and this is not legal advice, and you should
        check everything you do very carefully before you do it, and
        sometimes after.  Your mileage may vary, lower in California,
        and my employer owns his opinions, not mine.

>Tom O'Toole - ecf_stbo@jhuvms.hcf.jhu.edu - JHUVMS system programmer


Ehud

--
Ehud Gavron        (EG76)
Sunquest Network Manager
gavron@sunquest.com
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads