Slashdot Mirror


Theo de Raadt Responds to Linux Licensing Issues

bsdphx writes "While Theo may have a reputation of being "difficult" in some circles, this response to the recent relicensing controversy is thoughtful and well penned. Through this whole process I've learned some new things about both GPL and BSD licensing, and especially about combining the two."

1 of 455 comments (clear)

  1. Re:Just doesn't make sense by roman_mir · · Score: 5, Informative

    *scratches head*

            Your comment misses the point. What Theo claims (and he is right about it) is that by removing the BSD licence you don't contribute back to the BSD project that created the code you took. In other words you are doing just what you claim companies would be doing, because as soon as you put that under the GPL, the BSD project cannot use it anymore.

    Right, but the BSD in fact gives you the permission to do this
    - BSD does not let you remove the BSD license from the BSD code. Also NO license can supersede the copyright.

    BSD allows you to use the code in your own project, your own project can be then redistributed with BSD code in it, however the BSD license cannot be removed from the BSD code. BSD code can be modified but the BSD license cannot be removed from the modified file either. It is not possible to add a new license to a BSD licensed file without permission of the original copyright holders.

    However you can take BSD code, add it to your own project and distribute just the binaries of your project without giving any source code to anyone and it is not illegal under BSD. But BSD is a license and it cannot be legally removed from a licensed file.