commit | 2e47e9f871810c1fed0cd4093f64d9f94e4c6ec5 | [log] [tgz] |
---|---|---|
author | James Tucker <raggi@google.com> | Mon Dec 03 21:28:17 2018 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Dec 04 22:50:00 2018 +0000 |
tree | 5da1cec66b5723ad26d3e72e578c07f4e473ec41 | |
parent | cc2dcfff3bd87d09575c3a8b3ee5d9808f3ee14e [diff] |
[bin] export a working /bin in serial shells Originally we had planned to launch a fuchsia sys realm shell on serial, however this causes issues with tests and requires a more complex setup. Instead this solution should last until componentmgr takes charge. Test: cowsay works from serial shells. Bug: ZX-3043 #comment serial shells can run /bin trampolines. Change-Id: I219e1b585c23d9d15e7c4784755a4ee768301fc5
Zircon is the core platform that powers the Fuchsia OS. Zircon is composed of a microkernel (source in kernel/...) as well as a small set of userspace services, drivers, and libraries (source in system/...) necessary for the system to boot, talk to hardware, load userspace processes and run them, etc. Fuchsia builds a much larger OS on top of this foundation.
The canonical Zircon Git repository is located at: https://fuchsia.googlesource.com/zircon
A read-only mirror of the code is present at: https://github.com/fuchsia-mirror/zircon
The Zircon Kernel provides syscalls to manage processes, threads, virtual memory, inter-process communication, waiting on object state changes, and locking (via futexes).
Currently there are some temporary syscalls that have been used for early bringup work, which will be going away in the future as the long term syscall API/ABI surface is finalized. The expectation is that there will be about 100 syscalls.
Zircon syscalls are generally non-blocking. The wait_one, wait_many port_wait and thread sleep being the notable exceptions.
This page is a non-comprehensive index of the zircon documentation.