From: Yuliy Pisetsky <mentalchaos@cox.net>
To: Larry McVoy <lm@bitmover.com>
Cc: "Richard B. Johnson" <root@chaos.analogic.com>,
Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>,
Diego Calleja Garc?a <diegocg@teleline.es>,
Michael Bernstein <michael@seven-angels.net>,
gmicsko@szintezis.hu, LKML <linux-kernel@vger.kernel.org>
Subject: Re: SCO offers UnixWare licenses for Linux
Date: Thu, 24 Jul 2003 11:39:50 -0500 [thread overview]
Message-ID: <3F200BD6.3040304@cox.net> (raw)
In-Reply-To: <20030724160146.GF12647@work.bitmover.com>
Larry McVoy wrote:
>>At least in the United States, you are not going to get away with
>>claiming there is some stolen code that caused damages.
>>
>>
>...
>
>
>>Instead, to prevent this kind of "legal theft", the only thing a person
>>found in possession of "stolen" property needs to do is to return it,
>>unless there is evidence that the possessor actually stole the property
>>in question.
>>
>>
>
>Yeah, right.
>
> ``I "found" these 3GB of mp3's of music and I had no idea that
> they were stolen but now that you mention it, here they are back.
> Finders keepers, right?''
>
>What were you thinking? That's obviously incorrect, I know that it is
>incorrect from both observation of recent court cases as well as direct
>personal experience.
>
>
A more reasonable analogy is that you download a bunch of free programs
while one of them has some copy-righted music in it for sound effects.
Surely you'd have the ability to remove this once you found out without
penalty?
next prev parent reply other threads:[~2003-07-24 16:22 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 17:10 SCO offers UnixWare licenses for Linux Gabor MICSKO
2003-07-21 17:52 ` Michael Bernstein
2003-07-21 18:59 ` Diego Calleja García
2003-07-21 20:09 ` Richard B. Johnson
2003-07-21 20:36 ` Shawn
2003-07-24 14:52 ` Felipe Alfaro Solana
2003-07-24 15:08 ` Larry McVoy
2003-07-24 15:49 ` Sancar Saran
2003-07-24 19:32 ` Alan Cox
2003-07-25 11:44 ` Sancar Saran
2003-07-24 15:54 ` Richard B. Johnson
2003-07-24 16:01 ` Larry McVoy
2003-07-24 16:17 ` Tomas Szepe
2003-07-24 16:39 ` Yuliy Pisetsky [this message]
2003-07-24 16:55 ` Larry McVoy
2003-07-24 18:48 ` nick
2003-07-24 16:52 ` Ian Hastie
2003-07-24 17:22 ` Larry McVoy
2003-07-24 22:52 ` Stephan von Krawczynski
2003-07-24 17:00 ` David Benfell
2003-07-24 17:34 ` Felipe Alfaro Solana
2003-07-24 17:46 ` Shawn
2003-07-24 22:55 ` Jan Harkes
2003-07-24 23:27 ` Stephan von Krawczynski
2003-07-25 19:29 ` Timothy Miller
2003-07-24 21:03 ` Leandro Guimarães Faria Corsetti Dutra
2003-07-21 17:53 ` Jeff Sipek
2003-07-21 22:35 ` Brian McGroarty
2003-07-22 19:48 ` Jamie Lokier
2003-07-22 3:41 ` Kurt Wall
2003-07-21 17:24 Mudama, Eric
2003-07-22 23:34 Clayton Weaver
[not found] <20030724234213.GA20064@work.bitmover.com>
2003-07-25 0:11 ` Michael Bernstein
2003-07-25 0:21 ` Larry McVoy
2003-07-25 12:43 ` Jamie Lokier
2003-07-25 13:37 ` David S. Miller
2003-07-25 15:09 ` Yaroslav Rastrigin
2003-07-25 15:10 ` David S. Miller
2003-07-25 15:17 ` Larry McVoy
2003-07-25 13:37 Downing, Thomas
2003-07-26 8:21 Anuradha Ratnaweera
2003-07-26 14:49 ` Henrik Persson
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=3F200BD6.3040304@cox.net \
--to=mentalchaos@cox.net \
--cc=diegocg@teleline.es \
--cc=felipe_alfaro@linuxmail.org \
--cc=gmicsko@szintezis.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=michael@seven-angels.net \
--cc=root@chaos.analogic.com \
/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).