> GPLv3 came to being because of TiVO pulled off a similar thing, and required its kernels to be signed by their own private key. Actually TiVO didn't do that,

> GPLv3 came to being because of TiVO pulled off a similar thing, and required its kernels to be signed by their own private key. Actually TiVO didn't do that, instead they made their proprietary software running on top of Linux break when you modified Linux. The GPLv3 doesn't prevent that either, even though RMS wanted it to. Also, even GPLv2 requires users to be able to modify, rebuild and reinstall the vendor installed GPLed software. https://events19.linuxfoundation.org/wp-content/uploads/2017/11/Safely-Copylefted-Cars-Reexamining-GPLv3-Installation-Information-Requirements-ALS-Bradley-Kuhn-Behan-Webster-1.pdf https://events19.linuxfoundation.org/wp-content/uploads/2017... https://sfconservancy.org/blog/2021/mar/25/install-gplv2/ https://sfconservancy.org/blog/2021/mar/25/install-gplv2/ https://sfconservancy.org/blog/2021/jul/23/tivoization-and-the-gpl-right-to-install/ https://sfconservancy.org/blog/2021/jul/23/tivoization-and-t... Agreed with everything else in your post though.