fae63f4fa9
This patch simplifies the way of how Genode's base libraries are organized. Originally, the base API was implemented in the form of many small libraries such as 'thread', 'env', 'server', etc. Most of them used to consist of only a small number of files. Because those libraries are incorporated in any build, the checking of their inter-dependencies made the build process more verbose than desired. Also, the number of libraries and their roles (core only, non-core only, shared by both core and non-core) were not easy to capture. Hereby, the base libraries have been reduced to the following few libraries: - startup.mk contains the startup code for normal Genode processes. On some platform, core is able to use the library as well. - base-common.mk contains the parts of the base library that are identical by core and non-core processes. - base.mk contains the complete base API implementation for non-core processes Consequently, the 'LIBS' declaration in 'target.mk' files becomes simpler as well. In the most simple case, only the 'base' library must be mentioned. Fixes #18 |
||
|---|---|---|
| .. | ||
| README | ||
| main.cc | ||
| target.mk | ||
README
The 'fs_rom' server translates the 'File_system' session interface to the 'ROM' session' interface. Each request for a ROM file is handled by looking up an equally named file on the file system. If no such file could be found, the server watches the file system for the creation of the corresponding file. Furthermore, the server reflects file changes as signals to the ROM session. Limitations ----------- * Symbolic links are not handled * The server needs to allocate RAM for each requested file. The RAM is always allocated from the RAM session of the server. The RAM quota consumed by the server depends on the client requests and the size of the requested files. Therefore, one instance of the server should not be used by untrusted clients and critical clients at the same time. In such situations, multiple instances of the server could be used.