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

docs: update getstarted/disk

Browse Source
This commit is contained in:
lukas 2021-11-23 11:19:07 +00:00
parent 86f6a4236a
commit 1799bd5826
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
getstarted/disk.md
View File

@ -2,7 +2,7 @@
title: Get started with Phyllome OS title: Get started with Phyllome OS
description: description:
published: true published: true
date: 2021-11-23T11:17:29.284Z date: 2021-11-23T11:19:05.350Z
tags: tags:
editor: markdown editor: markdown
dateCreated: 2021-11-13T11:37:31.498Z dateCreated: 2021-11-13T11:37:31.498Z
@ -18,7 +18,7 @@ dateCreated: 2021-11-13T11:37:31.498Z
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.[^1] 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.[^1]
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 do not intent to provide automated ways to deploy guest operating systems (such as [Infrastructure as code solutions](https://en.wikipedia.org/wiki/Infrastructure_as_code) or an instance initialization software like [cloud-init](https://github.com/canonical/cloud-init)). 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 exeption of some RPM-based guests operating systems including Phyllome OS itself, does not intent to provide automated ways to deploy guest operating systems (such as [Infrastructure as code solutions](https://en.wikipedia.org/wiki/Infrastructure_as_code) or an instance initialization software like [cloud-init](https://github.com/canonical/cloud-init)).
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 defaults for each operating system. In this regard, its model is closer to [Promox](https://www.proxmox.com/en/), which doesn't make assumptions about how an operating system will be deployed. 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 defaults for each operating system. In this regard, its model is closer to [Promox](https://www.proxmox.com/en/), which doesn't make assumptions about how an operating system will be deployed.