roots/wiki
1
0
Fork 0
mirror of https://github.com/PhyllomeOS/wiki.git synced 2024-07-02 07:52:40 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: update deploy/rightforyou

Browse Source
This commit is contained in:
lukas 2022-01-07 10:52:34 +00:00
parent 0a3d8bdd26
commit c4e44b2d75
1 changed files with 10 additions and 36 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

46
deploy/rightforyou.md
View File

@ -2,7 +2,7 @@
title: Understand what you are signing up for
description:
published: true
date: 2022-01-07T10:51:52.896Z
date: 2022-01-07T10:52:31.901Z
tags:
editor: markdown
dateCreated: 2021-11-13T11:19:38.215Z
@ -10,44 +10,18 @@ dateCreated: 2021-11-13T11:19:38.215Z
# Is Phyllome OS right for you?
## Understand the Phyllome OS philosophy
## Phyllome OS Philosophy
> *Phyllome OS has one goal: to let users bring their favorite operating system and to run them well. Eventually, users should be able to reach **the state of virtual enlightenment** (tm), and stop worrying about the fact that their favorite operating system is running inside a virtual machine, just as humans should stop worrying about living in a computer simulation* ([perhaps?](https://en.wikipedia.org/wiki/Simulation_hypothesis)).
> Phyllome OS has one primarly goal: *to let users bring their favorite operating system and to run them well*.
By definition, the host, Phyllome OS, is trying to be as discrete as possible, so that users won't actually have to spend much time to manage it. Users should be able to spend their time using their favorite personal computing environment, rather than messing around with Phyllome OS itself. Although, we very much encourage you to [hack it](https://github.com/PhyllomeOS/phyllomeos#how-to-hack-phyllome-os).
* The host, Phyllome OS, is designed to be as discrete as possible.
* Phyllome OS should mostly take care of itself, so that users can spend their time using their favorite personal computing environment.
* That being said, we very much encourage users to [hack it](https://github.com/PhyllomeOS/phyllomeos#how-to-hack-phyllome-os), suggest new features and report bugs using [the issues system](https://github.com/PhyllomeOS/phyllomeos/issues).
* Eventually, users should be able to reach *the state of virtual enlightenment* (tm), which means accepting the fact that their favorite operating system is running inside a virtual machine, and being able to take advantage of that state of affairs.
However, if the host is meant to be a great place for guest operating systems to thrive, it is up to the user to manage the lifecycle of their guest operating system. Phyllome OS provides an optimized virtual machine model tuned to host modern operating systems, but, at the exception of some RPM-based guests operating systems including Phyllome OS itself, does not intent to provide automated ways to deploy guest operating systems (at the moment [Infrastructure as code solutions](https://en.wikipedia.org/wiki/Infrastructure_as_code) or instance initialization software like [cloud-init](https://github.com/canonical/cloud-init) do not seem generic enough to satisfy every modern desktop-based operating systems' idiosyncrasies).
In other words, contrary to end-to-end operating systems like [Qubes OS](https://www.qubes-os.org/) or the upcoming [Spectrum](https://spectrum-os.org/), which are offering ready to use templates or/and applications isolated in virtual machines by default, Phyllome OS delegates to end-users the task to install their favorite operating system, while trying to provide the best possible underlying defaults for each operating system. In this regard, its model is closer to [Proxmox](https://www.proxmox.com/en/), which doesn't make assumptions about how a guest operating system will be deployed.
## Assomptions
Phyllome OS makes a few assumptions, including the following ones:
* **Virtual machines have become viable personal computing environments, including for desktop computing**
* Due to their software-based nature, virtual machines are extremely flexible, and can for instance emulate features that their physical host may lack.
* **The host operating system should not be modified, in general**
* Two Phyllome OS hosts should barely differ, allowing virtual machines to be migrated from one host to the next.
## Limitations
Some limitations directly result from these assumptions.
Relying on a virtual machine as its primarily personal environment has key advantages, such as the ability to more easily migrate to a new host computer or the ability to create multiple virtual computers out of a single physical computer. However, it also comes with several limitations in comparison to using a bare-metal operating system. Some of these limitations will be tackled or greatly reduced one day, others might not.
### Performance-related
* **Performance overhead**. Phyllome OS requires resources to run, resources that will not be accessible to guest operating systems.
* **Suboptimal guest performance**. In most cases, running a virtual machine instead of using the physical hardware directly will come with a performance penalty. This penalty can be greatly reduced by using some techniques, such as letting the virtual machine access the underlying hardware directly, but this particular solution is by definition not scalable to multiple virtual machines.
### Usability-related
* **Limited features set**. Some operating systems are designed to leverage hardware features that may not be accessible to an operating system installed on a virtual machine, or that would require specific developments to be taken advantage of.
* **Increased general complexity**. Instead of running just an operating system on top of some physical hardware, any Phyllome OS user would need to manage it as well as their primarily guest operating system. As a result, it might be more difficult to troubleshoot an issue, and it will add a pile of code that the user has to trust.
* **Decreased general usability**. Any physical device attached to a computer won't automatically be made to a guest virtual machine. For some users, it might be considered a hindrance. Phyllome OS relies on Linux drivers. Not all hardware fully supports Linux well, which may force users to rely on device or controllers passthrough. Finally, the use of Phyllome OS will severely reduce your laptop battery-life.
> Phyllome OS has just started its journey and there is still a long, *years-long*, way to go to achieve its vision. It has several, [critical]() limitations.
[Support](/virt#guests) for guest systems differs widely. Have a look there
{.is-warning}
## Phyllome OS versions