All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Rudy Zijlstra <rudy@edsons.demon.nl>
Cc: Mark Junker <mjscod@gmx.de>, reiserfs-list@namesys.com
Subject: Re: where are reiser4 sources
Date: Wed, 23 Feb 2005 10:53:35 -0800	[thread overview]
Message-ID: <421CD12F.9020106@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0502231935400.20004@kheldar.edsons.demon.nl>

Rudy Zijlstra wrote:

>There is another issue here as well.
>
>Have you checked the Windows licenses (or rather the needed windows
>development kits) and what they allow you to do? If i remember correctly
>you run into problems there as well...
>
>If i remember correctly to interface with windows you have to include some
>SW from MS which is most definitly not GPL, and the license on those
>portions forbid using it with GPL SW.
>
>And this works from the GPL as well, because you cannot distribute the
>relevant windows code (i do not think you even have the source), you
>cannot distribute the complete set under GPL.
>
>I am open to be corrected here, but this is my understanding.
>
>Cheers,
>
>Rudy
>
>On Wed, 23 Feb 2005, Mark Junker wrote:
>
>  
>
>>Hans Reiser schrieb:
>>
>>    
>>
>>>The GPL says nothing about static linking.  You are making a
>>>derivative work.  No.
>>>      
>>>
>>Is it also forbidden to create a driver for a proprietary OS even when I
>>put the driver source under the GPL?
>>
>>    
>>
>>>Please contact my IP lawyer at brooke@artemama.com, and she will
>>>explain the penalties for violating copyright law.
>>>      
>>>
>>Oh, please don't be so rude. I didn't start the development yet.
>>
>>Regards,
>>Mark
>>
>>
>>
>>    
>>
>
>
>  
>
Thanks Rudy.  If MS wants Reiser4, they can damn well pay me a license 
fee for it.

  reply	other threads:[~2005-02-23 18:53 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21 16:16 where are reiser4 sources Mark Junker
2005-02-21 17:10 ` Sander Sweers
2005-02-21 17:59   ` Mark Junker
2005-02-22  2:08 ` David Masover
2005-02-22 15:20   ` Mark Junker
2005-02-22 18:41     ` Hans Reiser
2005-02-22 18:51       ` Valdis.Kletnieks
2005-02-23 17:10         ` Hans Reiser
2005-02-23 20:56           ` Mounting ReiserFS 3.6 RO increments journal count ? Linux Tard
2005-02-22 18:54       ` where are reiser4 sources Mark Junker
2005-02-23 17:19         ` Hans Reiser
2005-02-23 18:14           ` Mark Junker
2005-02-23 18:39             ` Rudy Zijlstra
2005-02-23 18:53               ` Hans Reiser [this message]
2005-02-23 21:06                 ` Mark Junker
2005-02-23 21:03               ` Mark Junker
2005-02-24 14:46                 ` Rudy Zijlstra
2005-02-25  4:34                   ` David Masover
2005-02-25  8:20                     ` Chester R. Hosey
2005-02-23 21:16               ` Mark Junker
2005-02-28 23:41                 ` Hans Reiser
2005-02-28 21:44                   ` Valdis.Kletnieks
2005-02-23 22:00           ` Jonathan Briggs
2005-02-24  0:58           ` David Masover
2005-02-22 18:56       ` Lehmann 
2005-02-22 17:49   ` Hans Reiser
2005-02-22 18:29     ` Mark Junker
2005-03-02  6:29 ` Alex Zarochentsev
  -- strict thread matches above, loose matches on Subject: below --
2005-03-01 16:52 Burnes, James

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=421CD12F.9020106@namesys.com \
    --to=reiser@namesys.com \
    --cc=mjscod@gmx.de \
    --cc=reiserfs-list@namesys.com \
    --cc=rudy@edsons.demon.nl \
    /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.