Why Fuchsia is not Linux
Summary
The Fuchsia documentation explains Zircon as a kernel of its own with object-based handles, message channels, jobs and capabilities instead of Linux APIs. Zircon grew out of the Little Kernel project. Fuchsia does not use a Linux kernel.
Ideas
- Zircon manages resources as kernel objects.
- Handles grant specific rights to these objects.
- Channels transfer messages and handles between processes.
- Jobs group processes and set shared policies.
Insights
- A new operating system can express security in its object model from the start.
- Handle-based rights make authority more explicit than global namespaces.
- Compatibility with Unix concepts does not mean a Linux architecture.
Facts
- Kernel objects have typed interfaces.
Recommendations
- Model rights per handle rather than per process across the board.
- Compare operating systems by their trust and object models.
References
Links to the original source and the Web Archive open in a new tab.