Hello!
On Sun, Sep 16, 2007 at 05:12:08PM -0400, Theodore Tso wrote:
>What is going on whenever someone changes a code is that they make a
Only if the additions/changes are significant enough to be copyrightable
on their own.
>Whether or not you can even make a derivative
> Redistribution and use in source and binary forms, with or without
>Note the "with or without modification". This is what allows people
Right. You may add nearly any copyright *on your own significant
additions/changes*. However, BSD/ISC explicitly requires to retain the
BSD/ISC terms, too (applicable to the original part of the combined
work).
>So for code which is single-licensed under a BSD license, someone can
No. The derivative work altogether has a *mixed* license. BSD/ISC for
the parts that are original, the other (restrictive, GPL, whatever)
license for the modifications/additions.
*If* you choose to distribute source along with the binaries, the part
of the source that's original is BSD/ISC licensed even in the derivative
work (though one may put *the additions/modifications* under restrictive
conditions, e.g. of commercial non-disclosure type source licensing).
>[... dual-licensing issues etc. already handled in other mails ...]
Kind regards,
Hannah.
| Greg Kroah-Hartman | [PATCH 005/196] Chinese: add translation of SubmittingDrivers |
| David Woodhouse | [PATCHv2 00/28] Allow built-in firmware to be accessed by request_firmware() |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Mike Travis | [RFC 00/15] x86_64: Optimize percpu accesses |
git: | |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Natalie Protasevich | [BUG] New Kernel Bugs |
| David Miller | [GIT]: Networking |
