roots/wiki
1
0
Fork 0
mirror of https://github.com/PhyllomeOS/wiki.git synced 2024-12-22 05:35:22 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: update phyllomeos/purpose

Browse Source
This commit is contained in:
lukas 2022-02-09 20:19:34 +00:00
parent 5ce200180b
commit ce0cfc9882
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
phyllomeos/purpose.md
View File

@ -2,7 +2,7 @@
title: Purpose title: Purpose
description: description:
published: true published: true
date: 2022-02-09T19:56:22.345Z date: 2022-02-09T20:19:32.002Z
tags: tags:
editor: markdown editor: markdown
dateCreated: 2021-11-12T15:31:30.659Z dateCreated: 2021-11-12T15:31:30.659Z
@ -14,23 +14,23 @@ The goal of Phyllome OS is to make it possible to run most operating systems loc
## Problematic ## Problematic
An operating system must possess drivers to allow it to interact with hardware components, devices or peripherals such as storage controllers, graphic cards or keyboards. Each driver has to be specifically written to work with a particular operating system. To support running most operating systems on a specific piece of hardware, one needs to develop and maintain a set of drivers for each one those operating systems. This is an almost insurmountable task as there are dozen unique operating systems out there. Most PC hardware is designed to work with a single operating system. Since the beginning, the end-users' freedom is serverly restricted, as the operating system is almost always preinstalled.[^1] Isn’t there a way to allow users to run their favorite operating system on most hardware?
Most of the time, users pick hardware that ships with their favorite operating system: most hardware is tied to a specific operating system. Therefore, user choice is severely restricted to only a certain set of computers [^1]. [^1]: Popular and proprietary operating systems such as macOS Big Sur or Windows 11 are optimized to only run on a limited set of computers. This state of affairs significantly limits users’ choice and may incite them to renew their hardware frequently, as operating systems providers may decide to drop support for older hardware models for any number of reasons.
Isn’t there a shortcut available, to allow users to run their favorite operating system on most hardware, provided that the operating system license allows it? [Virtualization](/virt/lexicon#virtualization) provides a partial answer to this question as it allows the abstraction of the underlying hardware, presenting generic software-based hardware to the operating system. In other words, by means of virtualization, a specific physical computer can be partially abstraced away and made to look generic to an operating system.
[^1]: Popular and proprietary operating systems such as macOS Big Sur or Windows 11 are optimized to only run on a limited set of computers. This state of affairs significantly limits users’ choice and may incite them to renew their hardware frequently, as operating systems providers may decide to drop support for older hardware models for any number of reasons. To be compatible with physical hardware, including USB controllers or graphic cards, one would still need to use a base operating system that can provide software to drive these physical devices.[^3] Most Linux distributions, including Fedora or Debian, ship with a large selection of such drivers, and as such represent another part of the solution to this problem.[^4]
[Virtualization](/virt/lexicon#virtualization) provides a partial answer to this problem as it allows the abstraction of the underlying hardware, presenting generic software-based hardware to the operating system. In other words, by means of virtualization, a specific physical computer can be abstraced away and made to look generic to an operating system. [^4]: The industry is even developing drivers for Linux first, at least for certain categories of components such as Network Interface Cards (NICs).
There are many types of virtualization. Phyllome OS is primarily focused on paravirtualization, which assumes that an operating system running in a virtualized environment is aware of being virtualized. For any operating systems to run well in such an environment, one would only have to focus on developing and maintaining a set of generic drivers for virtual hardware, a task that is well under way for many popular operating systems, including Linux-based, Darwin-based or Windows NT-based operating systems. [^3]: An operating system must possess drivers to allow it to interact with hardware components, devices or peripherals such as storage controllers, graphic cards or keyboards. Each driver has to be specifically written to work with a particular operating system. A specific piece of hardware requires a specific driver tailored for each operating systems out there. Achieving support across operating systems is an almost insurmountable task as there are dozen unique operating systems out there.
Virtualization, however, is only a partial answer to this problem. To be compatible with physical hardware, including USB controllers or graphic cards, one would still need to use a base operating system that can provide software to drive these physical devices. Most Linux distributions, including Fedora or Debian, ship with a large selection of such drivers, and as such represent another part of the solution to this problem. The industry is developing drivers for Linux first, at least for certain categories of components such as Network Interface Cards (NICs).
## In summary ## In summary
Let’s wrap it up: the idea behind Phyllome OS is to rely on Linux to provide drivers for specific hardware components and virtualization to provide a limited set of generic virtualized hardware that are already or could be made to work with most operating systems. The burden of hardware compatibility is put on Linux, freeing the operating system underneath, which would only need to provide generic virtual hardware drivers[^2]. The idea behind Phyllome OS is to rely on Linux to provide drivers for specific hardware components and virtualization[^5] to provide a limited set of generic virtualized hardware that are already or could be made to work with most operating systems. The burden of hardware compatibility is put on Linux, freeing the operating system underneath, which would only need to provide generic virtual hardware drivers[^2].
[^5]: There are many types of virtualization. Phyllome OS is primarily focused on paravirtualization, which assumes that an operating system running in a virtualized environment is aware of being virtualized. For any operating systems to run well in such an environment, one would only have to focus on developing and maintaining a set of generic drivers for virtual hardware, a task that is well under way for many popular operating systems, including Linux-based, Darwin-based or Windows NT-based operating systems.
[^2]: For instance, to provide storage block capacity, a developer of a specific operating system like Sculpt OS or ReactOS would only need to develop support for virtio-blk for its environment, and resort to Linux to interact with the hardware directly. [^2]: For instance, to provide storage block capacity, a developer of a specific operating system like Sculpt OS or ReactOS would only need to develop support for virtio-blk for its environment, and resort to Linux to interact with the hardware directly.