From: "Mathieu" <matt@minas-morgul.org>
To: "linux-os \(Dick Johnson\)" <linux-os@analogic.com>
Cc: "Christoph Hellwig" <hch@infradead.org>,
"Jan Engelhardt" <jengelh@linux01.gwdg.de>,
"Petr Vandrovec" <vandrove@vc.cvut.cz>,
"Grzegorz Piotr Jaskiewicz" <gj@kde.org.uk>,
<linux-kernel@vger.kernel.org>
Subject: Re: oops in VMWARE vmnet, on 2.6.12.x
Date: Tue, 06 Sep 2005 14:21:19 +0200 [thread overview]
Message-ID: <87ll2a4cao.fsf@barad-dur.minas-morgul.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0509060755180.20318@chaos.analogic.com> (linux-os@analogic.com's message of "Tue, 6 Sep 2005 08:11:23 -0400")
"linux-os \(Dick Johnson\)" <linux-os@analogic.com> disait dernièrement que :
are you serious or just on drugs ?
> On Tue, 6 Sep 2005, Christoph Hellwig wrote:
>
>> On Thu, Aug 11, 2005 at 08:17:28AM +0200, Jan Engelhardt wrote:
>>>
>>>> Nothing in the tarball mentiones any opensource license. If vmware is
>>
>> please read this sentence again. Just because somethings source is available
>> doesn't mean it's opensource.
>>
>
> Sure it is! It just isn't the GNU flavor of open source. It's likely
> that it's even "compatible" as long as it's not more restrictive
> than GNU.
>
> Often the "GNU protestants" are rejecting perfectly good work because
> they have adopted a highly restrictive religion, having been taught
> that it is the true meaning of freedom. Marx would be so proud!
>
> Wonderful thing about published private works, i.e., proprietary
> source-code, is that you can use it as a reference and write your
> own version(s). Since it's published, you don't need "clean-room"
> techniques. You just can't grab portions "whole cloth" and paste
> them into your source.
>
> When your driver, probably with improvements, is finished it
> is normal, but not necessary to provide some attribution in the
> source such as "Adapted from xxx.yyy.zzz" as a public "thank you".
>
>>>> actually using an opensource license please tell them to mention that
>>>> license and remove the propritary code markers.
>>>
>>> It's not opensource, but "proprietary and S_IRUGO". Though, the world won't
>>> fall down instantly if you change something [e.g. bugfix] and redistribute
>>> (with all the copyright stuff intact, and for non-profit)
>>
>
> Cheers,
> Dick Johnson
> Penguin : Linux version 2.6.13 on an i686 machine (5589.54 BogoMips).
> Warning : 98.36% of all statistics are fiction.
> .
> I apologize for the following. I tried to kill it with the above dot :
>
> ****************************************************************
> The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.
>
> Thank you.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
No fortunes found
next prev parent reply other threads:[~2005-09-06 12:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 15:44 Grzegorz Piotr Jaskiewicz
2005-08-09 15:50 ` Lee Revell
2005-08-09 15:53 ` Andreas Steinmetz
2005-08-09 15:56 ` Petr Vandrovec
2005-08-09 16:45 ` Christoph Hellwig
2005-08-11 6:17 ` Jan Engelhardt
2005-09-06 11:44 ` Christoph Hellwig
2005-09-06 12:11 ` linux-os (Dick Johnson)
2005-09-06 12:21 ` Mathieu [this message]
2005-09-06 12:44 ` linux-os (Dick Johnson)
2005-09-06 14:30 ` Grzegorz Piotr Jaskiewicz
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=87ll2a4cao.fsf@barad-dur.minas-morgul.org \
--to=matt@minas-morgul.org \
--cc=gj@kde.org.uk \
--cc=hch@infradead.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=vandrove@vc.cvut.cz \
/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
all inboxes | Powered by JetHome®