linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Leandro Guimar?es Faria Corsetti Dutra <lgcdutra@terra.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Switching to the OSL License, in a dual way.
Date: Sat, 26 Jul 2003 13:01:05 -0700	[thread overview]
Message-ID: <20030726200105.GA26271@work.bitmover.com> (raw)
In-Reply-To: <pan.2003.07.26.19.46.27.632068@terra.com.br>

On Sat, Jul 26, 2003 at 09:46:28PM +0200, Leandro Guimar?es Faria Corsetti Dutra wrote:
> On Sat, 26 Jul 2003 12:23:22 -0700, Larry McVoy wrote:
> > They tend to have the view "if you are being
> > a jerk and locking people into your application with no way to get at
> > their data, then of course reverse engineering is allowed, how else are
> > people to get at their data?  On the other hand, if you are being nice
> > and you provide documented ways for people to get at their data then
> > reverse engineering is not allowed".  Which seems to make sense, right?
> 
> 	No.  Reverse engineering is first a way of learning, then a
> safeguard... 

It's not clear to me that you have the right to learn how something
works if the producer of that something doesn't want you to learn it.
You seem to think differently, the laws don't seem to agree with you.

> 	Perhaps you are claiming the definition of protocols and data
> structures as protected by copyright.  Perhaps, but it doesn't make
> cloning less moral.  Laws and morals unfortunately are splitting
> farther and farther.

Perhaps that is because people who share your opinions can't seem to
understand that reverse engineering / copying is much easier than creating
in the first place and the people who spent the money on the creation need
to recoup that investment and make some profit so they can create again.

Maybe the warning bells should be ringing because your statements
are all about your "right" copying other people's work (I think it is
called plagerizing in some fields) rather than about creating new work.
If you spent less time copying and more time creating then we would be
following you rather then you attempting to (illegally) follow us.
Food for thought, dinner is served, eat up.
-- 
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm

  reply	other threads:[~2003-07-26 19:46 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24  8:40 Switching to the OSL License, in a dual way Dean McEwan
2003-07-24  8:58 ` Miles Bader
2003-07-24  9:46   ` Andre Hedrick
2003-07-24 18:06     ` Leandro Guimarães Faria Corsetti Dutra
2003-07-24 20:02       ` Andre Hedrick
2003-07-24 21:05         ` Leandro Guimarães Faria Corsetti Dutra
2003-07-24 21:57           ` Larry McVoy
2003-07-24 22:24             ` Leandro Guimarães Faria Corsetti Dutra
2003-07-25  9:56             ` Gaël Le Mignot
2003-07-25 14:39               ` Larry McVoy
2003-07-26  2:52                 ` Matthias Andree
2003-07-26  3:18                   ` Larry McVoy
2003-07-25 13:17             ` Jesse Pollard
2003-07-25 14:55               ` Larry McVoy
2003-07-25 15:15                 ` Gaël Le Mignot
2003-07-25 15:33                   ` Richard B. Johnson
2003-07-26 19:10             ` Rik van Riel
2003-07-26 19:23               ` Larry McVoy
2003-07-26 19:46                 ` Leandro Guimarães Faria Corsetti Dutra
2003-07-26 20:01                   ` Larry McVoy [this message]
2003-07-26 21:08                     ` Mr. James W. Laferriere
2003-07-26 20:21                 ` Bernd Eckenfels
2003-07-24  9:05 ` Leandro Guimarães Faria Corsetti Dutra
2003-07-27  9:21   ` Kai Henningsen
2003-07-24 11:30 ` viro
2003-07-24 10:35 Samium Gromoff
2003-07-24 11:51 Dean McEwan
2003-07-24 22:25 ` Stefan Reinauer
2003-07-25  9:34 Samium Gromoff
2003-07-25 13:27 ` Gaël Le Mignot
2003-07-25 15:33 John Bradford
2003-07-25 15:36 ` Valdis.Kletnieks
2003-07-26 19:46 Hank Leininger
2003-07-26 20:20 John Bradford

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=20030726200105.GA26271@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=lgcdutra@terra.com.br \
    --cc=linux-kernel@vger.kernel.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).