Fork us on GitHub Follow us on Facebook Follow us on Twitter

Changes between Version 57 and Version 58 of FAQ


Ignore:
Timestamp:
2017-11-01T21:40:03Z (23 months ago)
Author:
Jakub Jermář
Comment:

Update info on l4re

Legend:

Unmodified
Added
Removed
Modified
  • FAQ

    v57 v58  
    8686=== How is HelenOS different from L4Re? ===
    8787
    88 [http://l4re.org L4Re] is a multiserver operating system framework built on top of the Fiasco.OC microkernel. The kernel is capability-based and has real-time features. As of release !r72 from August 2016, L4Re runs on amd64, arm32, ia32, mips32 and mips64 processor architectures, supports SMP and specializes in virtualization. Above the microkernel runs a set of userspace components that fall into several categories: native L4Re components (such as the root and init tasks, I/O manager, drivers, GUI window manager and virtual machine monitors), or paravirtualized VMs (`L4Linux`), or fully-virtualized VMs, or third-party components serving demonstration purposes. The runtime scenarios are mostly (but not exclusively) statically setup by the init task and the I/O manager according to a pair of Lua scripts. L4Re provides a POSIX interface which allows it to use quite a few contributed packages. L4Re also uses a mixture of native and third party device driver and server components. Notably, the latter was historically enabled by the DDE framework which imported portions of Linux 2.6.29, allowing the reuse of compatible Linux device drivers. More recently, L4Re has used `L4Linux` and even fully-virtualized VMs as device driver OSes. `L4Linux` can be used also as a server component. The released version contains traces of a networking server that combines Linux NIC drivers, DDE and the lwIP networking stack. This component has been however disabled and marked broken as of release !r72.
     88[http://l4re.org L4Re] is a multiserver operating system framework built on top of the Fiasco.OC microkernel. The kernel is capability-based and has real-time features. As of release !r75 from October 2017, L4Re runs on amd64, arm32, arm64, ia32, mips32 and mips64 processor architectures, supports SMP and specializes in virtualization. Above the microkernel runs a set of userspace components that fall into several categories: native L4Re components (such as the root and init tasks, I/O manager, drivers, GUI window manager and virtual machine monitors), or paravirtualized VMs (`L4Linux`), or fully-virtualized VMs, or third-party components serving demonstration purposes. The runtime scenarios are mostly (but not exclusively) statically setup by the init task and the I/O manager according to a pair of Lua scripts. L4Re provides a POSIX interface which allows it to use quite a few contributed packages. L4Re also uses a mixture of native and third party device driver and server components. Notably, the latter was historically enabled by the DDE framework which imported portions of Linux 2.6.29, allowing the reuse of compatible Linux device drivers. More recently, L4Re has used `L4Linux` and even fully-virtualized VMs as device driver OSes. `L4Linux` can be used also as a server component. The previously released version contains traces of a networking server that combines Linux NIC drivers, DDE and the lwIP networking stack. This component has been however disabled and marked broken as of release !r72.
    8989
    9090In comparison, HelenOS supports a slightly different set of processor architectures and despite some experimental master theses' results does not currently engage in virtualization. Its kernel does not provide real-time guarantees. HelenOS' connection-oriented IPC is essentially a coarse-grained capability system for a single type of kernel objects: asynchronous IPC endpoints, known as answerboxes in HelenOS. HelenOS aims to provide a coherent, dynamic, single-user and generic-purpose system composed of many fine-grained components. HelenOS almost exclusively rolls its own original drivers, frameworks, GUI, networking and filesystems.