Introduction to Linux's License
summary
Explains that Linux’s effective license is GPLv2-only, documents many GPLv2 specifics (history, syscall exception, dual-licensing traces) and argues proprietary kernel modules usually look like derivative works. Emphasizes the technical compliance test: include complete corresponding source and working scripts used to control compilation and installation and then have an unfamiliar engineer try to build and install the shipped binary — if that fails it is not compliant. Describes enforcement hard cases and outcomes (examples of removal or rewrite).
AI-written summary · about
chapters (21)
- 0:00Intro
- 1:02Why should you care about legal issues
- 2:50What is a license
- 5:04Copyright Bias
- 6:58Free Software Licenses
- 7:17Copyleft
- 8:50GPL
- 9:56Copyrights
- 11:14Strong Copyleft
- 12:32Weak Copyleft
- 13:25Right to Modify
- 15:32Derivative Work
- 18:23Source Code
- 22:23CCS
- 24:15ISC
- 27:13Auto Upgrade Clause
- 29:37GPL v3
- 33:19Copyright law
- 35:52Lib GPIOD
- 37:18Dual Licensing
- 41:56Conclusion
related talks
43mSoftware Licensing and Compliance: It's All About Community
49mLicense to Kill One's Code
36mLicense Compliance in Embedded Linux with the Yocto Project
01h 03mFree Software: It's not about the license
48mWhat You Need to Know About Open Source - Trust Me, I'm a Lawyer
51mOpen Source License Compliance
41mHow to Choose an Open-Source License
49m"Installation Information" and GPLv3 & GPLv2 -- What Information Must you Provide, & What do you...