[lkml]   [2007]   [Sep]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: GPL weasels and the atheros stink
Daniel Hazelton <> writes:

> Then go yell at Mr. Floeter. The code is dual-licensed and he put
> BSD-License
> only code in it. Because that's the *EXACT* *SAME* thing you're talking
> about.

Actually it is not.

Dual BSD/GPL licence essentially means BSD, because rights given by
BSD are a superset of these by GPL.

You can legally take BSD code (or BSD/GPL, which is the same thing)
and include it in GPL project (or even in closed source one).

You can't legally take GPL code and include it in BSD project (or in
GPL/BSD), because GPL forbids derivative works distributed under less
(or more) restrictive licence than itself.

Being distributed under GPL/BSD legally equals "pure" BSD (BSD allows
restricting downstream, while GPL doesn't).

If some file in Linux reads "GPL/BSD" then it's, in fact, under BSD
licence. Crazy, isn't it? :-)

The other thing is copyright notices. I think one can't legally
alter someone else's licence conditions (in his/her name), unless
something like that is explicitly permitted.

However, we're talking about derivative works. A derivative
work may be, for example, GPL-licenced:

"Copyright (C) 1234 Joe the GPL lover
licenced under the GPL as published"

but could lawfully use code originally licenced under BSD:

"Portions copyright (C) 1234 Bill the BSD lover
originally licenced under no-ad BSD"

Thus his (Joe's) work is GPL only, but Bill's licence notice is
intact as required by it (BSD).

IANAL, maybe you (all of us) should consult one if required.
Krzysztof Halasa
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-09-03 19:21    [W:0.113 / U:6.164 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site