From: Russell Coker <russell@coker.com.au>
To: Ben McGinnes <bmcginnes@enternet.com.au>, selinux@tycho.nsa.gov
Subject: Re: A 'Statement of Assurance' on SELinux patents
Date: Thu, 8 Aug 2002 16:22:56 +0200 [thread overview]
Message-ID: <20020808142256.7DBB620B@lyta.coker.com.au> (raw)
In-Reply-To: <20020808235352.B4737@mail.enternet.com.au>
On Thu, 8 Aug 2002 15:53, Ben McGinnes wrote:
> [other good point about monopoly-potential in buying patent/SCC]
>
> Which is one very good reason, of course, for a more well-meaning
> group to purchase either the company or the patent; in order to prevent
> any future corporate travesty on the part of either SCC or anyone else
> they might sell the relevant patents to.
So if you behave badly then you get paid for doing so...
I prefer the model of channeling money to people who do good things. If a
company produces solid products, does the right thing, and contributes to the
community then you recommend them. If a company has great products but
doesn't contribute to the community and leaves legal issues etc in an unclear
state which costs people money then you should not deal with them. This
discourages bad behaviour, and is also sound practise.
Some years ago I recommended that a client make a significant investment in
Linux related hardware from a company that did not behave particularly well.
Since then the lack of support from the company (delayed releases supporting
new versions of software and configuration changes that aren't properly
documented making it difficult to migrate the config files) has been
continually delaying upgrades on the machine in question. The amount of time
that has been wasted due to that hardware has cost more than the purchase
price of the hardware.
I have learnt from that experience that the business ethics of a company you
deal with are quite important, especially months or years after purchase. I
will recommend to my clients that they spend more money for a product with
less features if it means better support (usually no-one uses all the
features of a product and the purchase price is often a small fraction of the
overall cost). Often the only way to determine the level of support you can
expect is to see how the company deals with the community (because by the
time you get accurate information it's way too late).
--
I do not get viruses because I do not use MS software.
If you use Outlook then please do not put my email address in your
address-book so that WHEN you get a virus it won't use my address in the
>From field.
--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2002-08-08 14:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 1:35 A 'Statement of Assurance' on SELinux patents Erich Allewohl
2002-08-06 3:48 ` Ed Street
2002-08-06 13:02 ` Russell Coker
2002-08-06 13:12 ` Ed Street
2002-08-06 14:15 ` Dale Amon
2002-08-06 14:32 ` Ed Street
2002-08-06 14:18 ` Russell Coker
2002-08-06 15:47 ` Shaun Savage
2002-08-07 3:21 ` Ben McGinnes
2002-08-07 12:38 ` James Griffin
2002-08-07 19:56 ` JW
2002-08-08 13:53 ` Ben McGinnes
2002-08-08 14:22 ` Russell Coker [this message]
2002-08-08 14:40 ` Joshua D. Guttman
2002-08-08 19:08 ` Edward J. Huff
2002-08-10 0:31 ` Ben McGinnes
2002-08-09 1:36 ` Rik van Riel
2002-08-06 12:57 ` Russell Coker
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=20020808142256.7DBB620B@lyta.coker.com.au \
--to=russell@coker.com.au \
--cc=bmcginnes@enternet.com.au \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.