Hi! On Sun, Sep 16, 2007 at 09:59:09PM +0200, Adrian Bunk wrote:JFTR, I do *not* think that that assessment was questionable. Unless the dual-licensing *explicitly* allows relicensing, relicensing is forbidden by copyright law. The dual-licensing allows relicensing only if that's *explicitly* stated, either in the statement offering the alternative, or in one of the licenses. Neither GPL nor BSD/ISC allow relicensing in their well-known wordings. If you think that's questionable, you should at least provide arguments (and be ready to have your interpretation of the law and the licenses tested before court). But the BSDl does not allow you to relicense the original code, even while it allows you to license copyrightable additions/modifications under different terms with few restrictions. However, you say "regarding ethics" and just go back to the legal level. Is it really ethical, if you consider both Linux and OpenBSD part of one OSS "community", to share things only in one direction? To take the reverse engineered HAL but to not allow OpenBSD to take some modifications back? A difference is, GPL requires it under every circumstance. BSD does not, indeed. But how should one expect it from *OSS* people that even *they* don't give back? Do you really want to put yourself on the same level as closed-source companies? Kind regards, Hannah. -
| Andrew Morton | -mm merge plans for 2.6.23 |
| Rafael J. Wysocki | [Bug #11207] VolanoMark regression with 2.6.27-rc1 |
| Zhang, Yanmin | AIM7 40% regression with 2.6.26-rc1 |
| Con Kolivas | [PATCH][RSDL-mm 0/7] RSDL cpu scheduler for 2.6.21-rc3-mm2 |
git: | |
| Gregory Haskins | [RFC PATCH 03/17] vbus: add connection-client helper infrastructure |
| David Woodhouse | [PATCH 03/30] solos: FPGA and firmware update support. |
| Natalie Protasevich | [BUG] New Kernel Bugs |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
