Operating system: Difference between revisions

Revision as of 08:34, 8 August 2024

Revision as of 06:25, 9 August 2024

Line 39:

===Library===

A library operating system (libOS) is one in which the services that a typical operating system provides, such as networking, are provided in the form of [[Library (computing)|libraries]] and composed with a single application and configuration code to construct a [[unikernel]]:<ref name="Unikernels">{{cite magazine

|last1=Madhavapeddy |first1=Anil

|last2=Scott |first2=David J

Line 51:

|url=https://doi.org/10.1145/2557963.2566628

|doi=10.1145/2557963.2566628

|access-date=2024-08-07}}</ref>: a specialized (only the absolute necessary pieces of code are extract from libraries and bound together<ref name="Unikraft-Build-Process">{{cite web

|url=https://unikraft.org/docs/concepts/build-process

|access-date=2024-08-08

Line 59:

|url-status=live}}</ref>), [[Single address space operating system|single address space]], machine image that can be deployed to cloud or embedded environments.

The operating system code and application code are not executed in separated [[Protection ring|protection domains]] (there is only a single application running, at least conceptually, so there is no need to prevent interference between applications) and OS services are accessed via simple library calls, without the usual overhead of [[Context switch|context switches]],<ref name="rise-of-libOS">{{cite web

|url=https://www.sigarch.org/leave-your-os-at-home-the-rise-of-library-operating-systems/

|access-date=2024-08-07

Line 67:

|archive-date=2024-03-01

|archive-url=https://web.archive.org/web/20240301072916/https://www.sigarch.org/leave-your-os-at-home-the-rise-of-library-operating-systems/

|url-status=live}}</ref>, in a way similarly to embedded and real-time OSes.

==History==