Episode Details
Back to Episodes526: Canonical Wins by Default
Published 2 years, 6 months ago
Description
While chaos is brewing in SUSE and Red Hat land, Canonical stays the course and doubles down on the Linux desktop. Plus, our thoughts on the kernel team GPL-blocking NVIDIA.
Sponsored By:
- Tailscale: Tailscale is a programmable networking software that is private and secure by default - get it free on up to 100 devices!
- Linode Cloud Hosting: A special offer for all Linux Unplugged Podcast listeners and new Linode customers, visit linode.com/unplugged, and receive $100 towards your new account.
- Kolide: Kolide is a device trust solution for companies with Okta, and they ensure that if a device isn’t trusted and secure, it can’t log into your cloud apps.
Links:
- jblive.fm — Jupiter Broadcasting Live Audio Stream
- 🎉 Alby — Boost into the show, first grab Alby, top it off, and then head over to the Podcast Index.
- ⚡️ LINUX Unplugged on the Podcastindex.org — You can boost from the web. Once Alby is topped off, visit our page on the Podcast Index.
- AMD Open-Source GPU Kernel Driver Above 5 Million Lines, Entire Linux Kernel At 34.8 Million
- Making life (even) harder for proprietary modules — It changes the behavior of symbol_get(), causing it to fail when asked to look up a symbol that is not marked GPL-only. This is an inversion of the usual test, which denies access to symbols that are marked GPL-only. The reasoning is that symbol_get() has always been intended for low-level cooperation deep within the kernel, where everything is expected to be GPL-only anyway.
- Linux 6.6 To Better Protect Against The Illicit Behavior Of NVIDIA’s Proprietary Driver — Back in 2020 when the original defense was added, NVIDIA recommended avoiding the Linux 5.9 for the time being. They ended up having a supported driver several weeks later. It will be interesting to see this time how long Linux 6.6+ thwarts their kernel driver.
- [Hacker News] Making life (even) harder for proprietary modules
- PATCH: modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules — Given that symbol_get was only ever inteded for tightly cooperating modules using very internal symbols it is logical to restrict it to being used on EXPORY_SYMBOL_GPL and prevent nvidia from costly DMCA circumvention of access controls law suites.
-
Listen Now
Love PodBriefly?
If you like Podbriefly.com, please consider donating to support the ongoing development.
Support Us