mirror of
https://github.com/genodelabs/genode.git
synced 2025-01-10 23:13:01 +00:00
f6dec901bb
It turns out that the name function does not have much use in practice except for naming the thread of the component's initial entrypoint. For dynamically linked components, this thread is created by the dynamic linker. It is named "ep" in these cases. Considering that we will eventually turn all regular components into dynamically linked executables, the additional information provided by the Component::name() function remains unused. So it is better to not bother the component developers with adding boilerplate code. |
||
|---|---|---|
| .. | ||
| doc | ||
| include | ||
| lib/mk | ||
| run | ||
| src | ||
| README | ||
This is the example operating system based on the Genode OS framework: :_Init_: is the first real process in the system. The provided implementation uses a very simple XML parser to read its configuration files. :_Drivers_: The example OS has basic drivers for frame buffer, mouse and keyboard input, the PCI bus, the real-time clock, and system-specific timers. :_Server_: The only server in the example OS is Nitpicker, a minimal-complexity GUI server. :_Test_: are also part of the example OS. You may have a look at the fork bomb as a simple system stress test. :_Ldso_: is the dynamic linker used for loading executables that are linked against shared libraries. :_Lib_: contains libraries used by the components of the OS repository, for example, the alarm framework.