On 12 Sep 2024, at 06:41, Hugo V.C. <skydivebcn@gmail.com> wrote:
"I don’t think tutorials on microkernels and capabilities belong into
Well, people usually like to understand how things work, moreover on a system like seL4. And, whether you like or not, there will be forks, hacks, modifications... the more info you provide, the more involved the community will be. Frameworks are a must to speed up real life adoption, but ideally, all the low level info must be clear and the easier the better. I used to pentest an RTOS derivative of VxWorks on top of some Marvel Armada cpus, at the beginning with public very abstract info, but the fun came when I got (legit) access to confidential low level cpu specs of the different models... then I undestood why some fault injection attacks were being successful. Developers can do their job with just Mikrokit, but many of them, will have curiosity to understand why they need to do things the way they are forced. By being able to fully understand how things really work at low level, they get more involved, they can also contribute with improvements, and, hopefully, they will be happier than just blindly trust. It's about letting the door open to developers and engineers to learn at deeper level, as easy as possible. Maybe a door some people will never open, but for those who dare to open, would be nice to be sure they get engaged. On Wednesday, September 11, 2024, Gernot Heiser via Devel <devel@sel4.systems> wrote: the seL4 kernel documentation"
Sure. I have no idea how you guys can deal with this... I'm on the
commercial side, just thinking about how people can "easily" become seL4 developer…
How is this affected by low-level technical details that are hidden behind libraries, especially if you use higher-level frameworks such as the Microkit?
Gernot
_______________________________________________ Devel mailing list -- devel@sel4.systems To unsubscribe send an email to devel-leave@sel4.systems