this post was submitted on 10 Sep 2024
91 points (91.7% liked)

Linux

5242 readers
124 users here now

A community for everything relating to the linux operating system

Also check out !linux_memes@programming.dev

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 1 year ago
MODERATORS
 

Linux maintainers are unwilling to get rust into the kernel, so some rust folks decided to start writing a new kernel with same ABI. This allows them to make new architectural decisions. An example being their "frame kernel" (something between a monolithic kernel and a microkernel).

If I may say, it's more legible and the tooling is way better, right off the bat.

you are viewing a single comment's thread
view the rest of the comments
[–] mmstick@lemmy.world 4 points 2 months ago* (last edited 2 months ago) (2 children)

All source code in Rust is statically-linked when compiled, which thereby renders the LGPL no different from the GPL in practice. For Rust, the MPL-2.0 is a better license because it does not have the linking restriction.

[–] qaz@lemmy.world 1 points 2 months ago

Interesting. Is that because the kernel can't load a a module as dylib (I don't know a lot about kernel development) or because dylibs are also somehow statically linked in Rust?

[–] qaz@lemmy.world 1 points 2 months ago

Huh, I didn't know that. I thought dylibs could just be linked normally. Thanks for the insight.