L4Env: Difference between revisions

From TUDOS-Wiki
Jump to navigationJump to search
BjoernD (talk | contribs)
→‎What it provides: Some servers already have good docs
m Reverted edits by Ogozasuta (talk) to last revision by Adam
 
(4 intermediate revisions by 2 users not shown)
Line 19: Line 19:
* System bootup services (bootstrap, roottask, etc.)
* System bootup services (bootstrap, roottask, etc.)
* [http://os.inf.tu-dresden.de/l4env/doc/html/names/index.html Names]: basic name service
* [http://os.inf.tu-dresden.de/l4env/doc/html/names/index.html Names]: basic name service
* Dynamic application startup (loader, tftp, bmodfs)
* Dynamic application startup (loader, ldso, tftp, bmodfs)
* [[LibC | C library]] (port of a subset of the uClibc)
* [[LibC | C library]] (port of a subset of the uClibc)


Line 25: Line 25:


* [[L4VFS]]: virtual console (vt100) support, higher level name service, basic file server, many more
* [[L4VFS]]: virtual console (vt100) support, higher level name service, basic file server, many more
* ports of different graphic libraries: [[Qt | Qt3]], [[Qt | Qt4]], [[SDL]], etc.
* ports of different graphic libraries like [[Qt | Qt3]]
* console system: l4con
* basic window manager: [[Nitpicker]], [[DOpE]]
* basic window manager: [[Nitpicker]], [[DOpE]]
* signal: POSIX signalling mechanism
* signal: POSIX signalling mechanism
Line 33: Line 34:
* pthread library
* pthread library
* full file system support
* full file system support
* a full POSIX system


===Further information===
===Further information===


* [http://www.inf.tu-dresden.de/index.php?node_id=1587 L4Env manuals] (generated from current SVN sources)
* [http://www.inf.tu-dresden.de/index.php?node_id=1587 L4Env manuals] (generated from current SVN sources)

Latest revision as of 22:26, 24 November 2010

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

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 like Qt3
  • console system: l4con
  • basic window manager: Nitpicker, DOpE
  • signal: POSIX signalling mechanism

What it does not provide

  • pthread library
  • full file system support
  • a full POSIX system

Further information