4 ms·
Use the source, Luke. I'm not usually one to trot out that line, but I've found it is the simplest way to figure out what's going on. Most subsystems are prett
by adestefan 13y ago
Use the source, Luke.
I'm not usually one to trot out that line, but I've found it is the simplest way to figure out what's going on. Most subsystems are pretty straight forward. The only really hairy place is the scheduler. That's after mucking with most of the device model, ARM specific bits, and networking stack.
- leccine 13y agoIt is not only that but he does not like to organize code in a good way and does not care about security too much either. Pax team was asking him to merge in the security patches to mitigate some of the problems inherited from the monolithic design and the lack of kernel and user space memory separation but those efforts were greatly ignored. On the top of these he is suffering from not-invented here attitude (to be fair this is common in the open source community) and license problems as well. This is why everything gets re-implemented in Linux, prime example is dtrace vs. opentap. I think the world deserves a better kernel that is designed for the modern era, security and maintainability kept in mind. There are some interesting work done in few projects already: https://github.com/cloudius-systems/osv https://github.com/cloudius-systems/osv https://os.inf.tu-dresden.de/L4/ https://os.inf.tu-dresden.de/L4/