> The main issue I have with microkernels is that they don't solve any problem that I have.
> The main issue I have with microkernels is that they don't solve any problem that I have. > > […] > > Do microkernels offer any application-visible features that I don't have today with Linux? To the best of my knowledge they do not. Don't you hate having to upgrade your whole kernel (memory manager, scheduler, fs, network stack) just to fix a small-but-annoying problem with your GPU (for example tearing)? With a microkernel you could update that driver without updating the rest of the kernel, or of the OS. Yes "OS", because an update of the kernel often requires an update of the corresponding user-space programs (lmsensors, libdrm, mesa, X11, libalsa, iptables). If our systems were built upon microkernels and developed with strict boundaries between components it would be much easier to maintain them. However I think Torvarlds has a point when it says that going down the path of microkernels means turning many low-level problems into IPC problems, most of which are not yet solved or not solved in a way that is compatible (performance-wise) with current hardware. Let's hope research and the brewing libre hardware community will tackle this problem.
Posted by gioele on Jan 2, 2016, 11:03 AM
Tags
Related issues
- I can't recall who said it, but "The biggest problem with golden ages is that you never realize you're in one until it's over".
- [BUG] No response from API error when Advisor is triggered
- I thought the general premise is that humans can't form social groups bigger than around ~200.
- great, now can we convince the rest of the internet to start adding AAAA records and ipv6 endpoints for things.
- > It's only with the emergence of whiny, persnickety Unix devs who refused to leave the comforting embrace of their editor of choice that...
- Contrary to some other comments: no, IPV6 hasn't taken over the world at all.
Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments
reliability (Network)
I can't recall who said it, but "The biggest problem with golden ages is that you never realize you're in one until it's over".
[BUG] No response from API error when Advisor is triggered
I thought the general premise is that humans can't form social groups bigger than around ~200.
great, now can we convince the rest of the internet to start adding AAAA records and ipv6 endpoints for things.
> It's only with the emergence of whiny, persnickety Unix devs who refused to leave the comforting embrace of their editor of choice that...
Contrary to some other comments: no, IPV6 hasn't taken over the world at all.
Copy and paste not working
Full Offline Support
> The main issue I have with microkernels is that they don't solve any problem that I have.
> The main issue I have with microkernels is that they don't solve any problem that I have. > > […] > > Do microkernels offer any application-visible features that I don't have today with Linux? To the best of my knowledge they do not. Don't you hate having to upgrade your whole kernel (memory manager, scheduler, fs, network stack) just to fix a small-but-annoying problem with your GPU (for example tearing)? With a microkernel you could update that driver without updating the rest of the kernel, or of the OS. Yes "OS", because an update of the kernel often requires an update of the corresponding user-space programs (lmsensors, libdrm, mesa, X11, libalsa, iptables). If our systems were built upon microkernels and developed with strict boundaries between components it would be much easier to maintain them. However I think Torvarlds has a point when it says that going down the path of microkernels means turning many low-level problems into IPC problems, most of which are not yet solved or not solved in a way that is compatible (performance-wise) with current hardware. Let's hope research and the brewing libre hardware community will tackle this problem.
Comments (0)
No comments yet. Start the discussion.