<div>Sorry, bad phrasing & terminology, I didn't mean it in the way I think maybe you read though. I.e not meaning that it was in the public domain, just that once its under the GPL it has to follow the GPL license whatever (
i.e you couldn't take lines of code out of it without it still being distributed under the GPL itself, causing their own code to follow it).</div>
<div> </div>
<div>I'm just not seeing the GPL or linux really being the issue as such or even coming into it. My guess is more that we'll see more integrated non GPL proprietary solutions, like Windows server version x containing virtualised Suse server (or feature), with the none GPL part being the issue. This can be done fine (to my understanding) since the agreement without any problems, not related to GPL (whereas there would be an issue with certain other distros, again relating to proprietary code, not GPL).
</div>
<div> </div>
<div>Not sure if thats making sense or not.<br><br> </div>
<div><span class="gmail_quote">On 11/18/06, <b class="gmail_sendername">Andrew Guard</b> <<a href="mailto:andrew@andrewguard.com">andrew@andrewguard.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>> Interesting discussion, was hoping something like this may get discussed<br>> at<br>> some point, just so I can understand it better myself (often get in a
<br>> muddle<br>> with gpl).<br>><br>> My understanding would be though that the kernel would not contain any<br>> copyrighted suse code ? (even if they have worked on it, the bits they did<br>> would be under the gpl, which is different to their proprietary code with
<br>> their distro release, haven't they effectively given up any copyright ?).<br><br>GPL is nothing about giving up copyright. In fact without Copyright ie<br>Public Domain the GPL would be unenforceable. When it Public Domain you
<br>can do as you please and doesn't matter what anyone says about it because<br>it in the Public Domain. Now Public Domain is rather interesting because<br>if it in Public Domain you tomorrow could claim you own the copyright and
<br>do as you please. If want to release your works in Public Domain then<br>there is the MIT licence. It not a licence as such but notice that it be<br>release in to the Public Domain.<br><br><br>Anyway I think you should read what says at this site:-
<br><a href="http://www.kernel.org/pub/linux/kernel/COPYING">http://www.kernel.org/pub/linux/kernel/COPYING</a><br><br><br>--<br>This e-mail has been edited with a webmail service.<br><br><br><br>__<br>Sussex mailing list
<br><a href="mailto:Sussex@mailman.lug.org.uk">Sussex@mailman.lug.org.uk</a><br>E-mail Address: <a href="mailto:sussex@mailman.lug.org.uk">sussex@mailman.lug.org.uk</a><br>Sussex LUG Website: <a href="http://www.sussex.lug.org.uk/">
http://www.sussex.lug.org.uk/</a><br><a href="https://mailman.lug.org.uk/mailman/listinfo/sussex">https://mailman.lug.org.uk/mailman/listinfo/sussex</a><br></blockquote></div><br>