| 88 | | [http://l4re.org L4Re] is a multiserver operating system 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 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 driver OSes. 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 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. |
