How will fixing only C part work with the "do not break user space" policy?
How will fixing only C part work with the "do not break user space" policy?
Posted Jun 25, 2024 11:57 UTC (Tue) by pizza (subscriber, #46)In reply to: How will fixing only C part work with the "do not break user space" policy? by pbonzini
Parent article: Rust for filesystems
> I'm not talking of a full-scale migration; a non-trivial or undeniable level of adoption is enough.
In other words, "The inevitability of Rust becoming a requirement to build a usable/useful kernel."
...All it takes is one driver (not even subsystem), and *BAM* you're now a Rust system with a (substantial) pile of C.
(Or rather, "kernel-Rust" with a pile of "kernel-C")
The LWN site is currently under high scraper load, so comment display has been suppressed for anonymous users. If you are a human, you may read the comments by clicking the button below:
Note: you can avoid this step in the future by logging into your LWN account.