Mass replace "StandaloneVM" with "standalone"

Also updates the "Standalones and HVM" page.

QubesOS/qubes-issues#1015
This commit is contained in:
Andrew David Wong 2021-06-18 02:29:28 -07:00
parent 63498a6c17
commit 2ae0ce9524
No known key found for this signature in database
GPG key ID: 8CE137352A019A17
10 changed files with 48 additions and 49 deletions

View file

@ -81,13 +81,13 @@ Debian also has three Qubes VM testing repositories (where `*` denotes the Relea
To enable or disable any of these repos permanently, uncomment the corresponding `deb` line in `/etc/apt/sources.list.d/qubes-r*.list`.
### StandaloneVMs
### Standalones
When you create a [StandaloneVM](/doc/standalone-and-hvm/) from a template, the StandaloneVM is a complete clone of the template, including the entire filesystem.
After the moment of creation, the StandaloneVM is completely independent from the template.
When you create a [standalone](/doc/standalone-and-hvm/) from a template, the standalone is a complete clone of the template, including the entire filesystem.
After the moment of creation, the standalone is completely independent from the template.
Therefore, it will not be updated when the template is updated.
Rather, it must be updated individually.
The process for installing and updating software in StandaloneVMs is the same as described above for templates.
The process for installing and updating software in standalones is the same as described above for templates.
### RPMFusion for Fedora templates

View file

@ -34,7 +34,7 @@ Fully updating your Qubes OS system means updating:
- [Dom0](/doc/how-to-install-software-in-dom0/)
- [templates](/doc/how-to-install-software/#updating-software-in-templates)
- [StandaloneVMs](/doc/how-to-install-software/#standalonevms) (if you have any)
- [standalones](/doc/how-to-install-software/#standalones) (if you have any)
You can accomplish this using the **Qubes Update** tool.
@ -56,14 +56,14 @@ Even if no updates have been detected, you can use this tool to check for update
The above covers updating *within* a given operating system release.
Eventually, however, most operating system releases will reach [end-of-life (EOL)](https://fedoraproject.org/wiki/End_of_life), after which point they will no longer be supported.
This applies to [Qubes OS itself](/doc/supported-versions/#qubes-os) as well as operating systems used for templates and StandaloneVMs, such as [Fedora](/doc/templates/fedora/) and [Debian](/doc/templates/debian/).
This applies to [Qubes OS itself](/doc/supported-versions/#qubes-os) as well as operating systems used for templates and standalones, such as [Fedora](/doc/templates/fedora/) and [Debian](/doc/templates/debian/).
It is very important to use only supported releases, since generally only supported releases receive security updates.
This means that you must periodically upgrade to a newer release before your current release reaches EOL.
In the case of Qubes OS itself, we will always [announce](/news/categories/#releases) when a given Qubes OS release is approaching and has reached EOL, and we will provide [instructions for upgrading to the next stable supported Qubes OS release](/doc/upgrade/).
Again, you can always see the current support status for all Qubes OS releases [here](/doc/supported-versions/#qubes-os).
Periodic upgrades are also important for templates and StandaloneVMs.
Periodic upgrades are also important for templates and standalones.
For example, you might be using a [Fedora Template](/doc/templates/fedora/).
The [Fedora Project](https://getfedora.org/) is independent of the Qubes OS Project.
They set their own [schedule](https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule) for when each Fedora release reaches EOL.