L4Env: Difference between revisions
m add link to manuals |
→What it provides: start links to not-yet existing subpages |
||
Line 11: | Line 11: | ||
===What it provides=== | ===What it provides=== | ||
* thread startup and termination | * [[l4thread|L4 Threads]]: thread startup and termination, thread-local storage | ||
* task startup and termination | * [[Task server]] / [[hierarchical task interface]]: task startup and termination | ||
* memory management (pager, malloc, free) | * [[Dataspace Managers]]: memory management (pager, malloc, free) | ||
* services | * System bootup services (bootstrap, roottask, etc.) | ||
* basic name service | * [[Names]]: basic name service | ||
* | * Dynamic application startup (loader, tftp, bmodfs) | ||
* C library (port of a subset of the uClibc) | * [[LibC | C library]] (port of a subset of the uClibc) | ||
More complex services are provided in additional packages: | More complex services are provided in additional packages: | ||
* | * [[L4VFS]]: virtual console (vt100) support, higher level name service, basic file server, many more | ||
* ports of different graphic libraries: | * ports of different graphic libraries: [[Qt | Qt3]], [[Qt | Qt4]], [[SDL]], etc. | ||
* basic window manager: | * basic window manager: [[Nitpicker]], [[DOpE]] | ||
* signal: POSIX signalling mechanism | |||
===What it does not provide=== | ===What it does not provide=== |
Revision as of 11:26, 4 September 2007
The L4 Environment, short L4Env, is a programming environment for applications that should run on the L4.Fiasco kernel. L4Env was developed to provide basic building blocks such as a C library or memory management.
Reasoning
Prior to L4Env application developer wrote their software to use the basic mechanisms provided by the L4 microkernel. These included software to provide functions, such as malloc, free, printf, etc. Because, the implementations were mostly similar and application developers should be writing applications, instead of support libraries, these software was combined into a programming environment.
Now that the L4Env provided basic functionality, more applications and more sophisticated software could be made run on L4.
L4Env might not be perfect and contain all the functionality someone might require, it has proven to be a stable basis. And, as demand requires, it grows to include more functionality.
What it provides
- L4 Threads: thread startup and termination, thread-local storage
- Task server / hierarchical task interface: task startup and termination
- Dataspace Managers: memory management (pager, malloc, free)
- System bootup services (bootstrap, roottask, etc.)
- Names: basic name service
- Dynamic application startup (loader, tftp, bmodfs)
- C library (port of a subset of the uClibc)
More complex services are provided in additional packages:
- L4VFS: virtual console (vt100) support, higher level name service, basic file server, many more
- ports of different graphic libraries: Qt3, Qt4, SDL, etc.
- basic window manager: Nitpicker, DOpE
- signal: POSIX signalling mechanism
What it does not provide
- pthread library
- full file system support
Further information
- L4Env manuals (generated from current SVN sources)