Oct 15, 2026, 5:03 PMhttps://doc.redox-os.org/book/microkernels.html
redox has some information about this, probably because their OS uses one.
- Oct 15, 2026, 5:03 PM
Replies
argv[-1]argv_minus_one@mastodon.sdf.orgOct 15, 2026, 5:13 PMYeah, what they're doing is neat. That ought to solve the whole “out-of-tree drivers aren't compatible with future kernels” problem.
- Oct 15, 2026, 5:13 PM
@argv_minus_one i wouldn't know anything about driver support via the kernel, so I will take your word for it, unless you were being sarcastic, in which case I wont :3
- argv[-1]argv_minus_one@mastodon.sdf.orgOct 15, 2026, 5:26 PM
I'm referring to the situation on Linux. Most drivers are bundled with Linux, and those that are not bundled with Linux have to be continuously maintained, because Linux is often changed internally in ways that makes old drivers not work any more.
Redox, on the other hand, has a well-defined interface for drivers that isn't ever-shifting, so a driver that works on Redox today will probably still work a year later, without even recompiling let alone changing the code.
- argv[-1]argv_minus_one@mastodon.sdf.orgOct 15, 2026, 5:28 PM
You know how daemons on Linux etc don't have to be recompiled and will just keep working on future kernel versions? On Redox, drivers are daemons.
- Oct 15, 2026, 5:50 PM
@argv_minus_one that's a neat bit of information to know, thanks for sharing it!