27 ms·
>What license could he have used that would have prevented the thing Intel did? GPLv3: https://www.gnu.org/licenses/rms-why-gplv3.en.html https://www.gnu.org/l
by ac29 9y ago
>What license could he have used that would have prevented the thing Intel did?
GPLv3: https://www.gnu.org/licenses/rms-why-gplv3.en.html https://www.gnu.org/licenses/rms-why-gplv3.en.html
Specifically: "One major danger that GPLv3 will block is tivoization. Tivoization means certain “appliances” (which have computers inside) contain GPL-covered software that you can't effectively change, because the appliance shuts down if it detects modified software. The usual motive for tivoization is that the software has features the manufacturer knows people will want to change, and aims to stop people from changing them. The manufacturers of these computers take advantage of the freedom that free software provides, but they don't let you do likewise."
- akerl_ 9y ago"But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM)." In our hypothetical (and I suspect in reality), the code doing scary/concerning things sits in userspace on top of MINIX, so they'd just have to constrain their updates to that system.