Re: module license taints kernel.

2007-12-03 Thread David Schwartz
On Dec 3, 7:28 am, J de Boyne Pollard <[EMAIL PROTECTED]> wrote: > No. What is required in order to run a work distributed as source > code is _compiliation_, from source code to machine code. If you compile without linking, you'll be left with an object file, which you can't execute. Ordinary u

module license taints kernel.

2007-12-03 Thread J de Boyne Pollard
DS> You will [not] find anything about DS> "larger programs" or linking in copyright law. JdeBP> You will, however, find a definition of an JdeBP> "adaptation" of a computer program in JdeBP> section 21 of the U.K. Copyrights, JdeBP> Designs, and Patents Act (as amended). DS> I don't know enough

module license taints kernel.

2007-11-30 Thread J de Boyne Pollard
LP> And I think you _are_ making copies already by LPI> downloading the program from kernel.org (at LPI> least that is the case legally where I live). DS> Nope. One copy flows over the network, is converted DS> to the copy on your disk, and that's that. One copy is DS> all there is. The person who

Re: module license taints kernel.

2007-11-26 Thread David Schwartz
On Nov 26, 9:30 am, J de Boyne Pollard <[EMAIL PROTECTED]> wrote: > DS> You will [not] find anything about > DS> "larger programs" or linking in copyright law. > You will, however, find a definition of an "adaptation" of a computer > program in section 21 of the U.K. Copyrights, Designs, and Pate

module license taints kernel.

2007-11-26 Thread J de Boyne Pollard
DS> You will [not] find anything about DS> "larger programs" or linking in copyright law. You will, however, find a definition of an "adaptation" of a computer program in section 21 of the U.K. Copyrights, Designs, and Patents Act (as amended). ___ gnu-m