Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-10-01 01:25:40 -04:00
Code Issues Packages Projects Releases Wiki Activity

Clarify definitions

Browse Source
This commit is contained in:
Andrew David Wong 2021-06-18 12:08:33 -07:00
parent 325abc8cc3
commit b3c61ed5c0
No known key found for this signature in database
GPG Key ID: 8CE137352A019A17
1 changed files with 48 additions and 47 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

95
user/reference/glossary.md
View File

@ -12,64 +12,59 @@ title: Glossary
## app qube
Any [qube](#qube) that depends on a [template](#template) for its root
Any [qube](#qube) that does not have a root filesystem of its own. Every app
qube is based on a [template](#template) from which it borrows the root
filesystem.
* Technical note: This is the preferred user-facing term replacing the
deprecated terms "AppVM" and "TemplateBasedVM."
* Historical note: This term originally meant "a qube intended for running user
software applications" (hence the name "app").
* Historical note: This is the preferred term replacing the deprecated term
"TemplateBasedVM."
## disposable
See [How to Use Dispoables](/doc/how-to-use-disposables/). A temporary [app
qube](#app-qube) based on a [disposable template](#disposable-template) that
can quickly be created, used, and destroyed.
See [How to Use Dispoables](/doc/how-to-use-disposables/). A type of temporary
[app qube](#app-qube) that can quickly be created, used, and destroyed. Each
disposable is based on a [disposable template](#disposable-template).
## disposable template
A type of [app qube](#app-qube) on which [disposables](#disposable) are based.
(Not to be confused with the concept of a [template](#template) that is itself
disposable, which does not exist in Qubes OS.)
(Not to be confused with the concept of a regular [template](#template) that is
itself disposable, which does not exist in Qubes OS.)
Disposable templates are not [templates](#template), since (being app qubes)
they do not have root filesystems of their own to provide to other qubes.
Rather, disposable templates are complementary to templates insofar as
disposable templates provide their own user filesystems to the disposables
based on them.
* Disposable templates must be app qubes. They cannot be regular
[templates](#template).
* Each [disposables](#disposable) is based on a disposable template, which is
in turn based on a regular [templates](#template).
## dom0
[Domain](#domain) Zero. Also known as the **host** domain, dom0 is the initial
[Domain](#domain) zero. Also known as the **host** domain, dom0 is the initial
qube started by the Xen hypervisor on boot. Dom0 runs the Xen management
toolstack and has special privileges relative to other domains, such as direct
access to most hardware.
* The term "dom0" is not a proper noun and should not be capitalized unless
it's the first word in a sentence.
* The use of [domain](#domain) as a synonym for [VM](#vm) is specific to Xen.
Qubes diverges from this practice. See: [domain](#domain).
* The term "dom0" is not a proper noun. It should follow the capitalization
rules of common nouns.
## domain
_This term is deprecated in the context of Qubes OS._
In Xen, a synonym for [VM](#vm). See ["domain" on the Xen
Wiki](https://wiki.xenproject.org/wiki/Domain).
* This term has no official meaning in the context of Qubes OS.
## domU
Unprivileged [domain](#domain). Also known as **guest** domains, domUs are the
counterparts to dom0. In Xen, all VMs except dom0 are domUs. By default, most
domUs lack direct hardware access.
* The term "domU" is not a proper noun and should not be capitalized unless it
is the first word in a sentence.
* The use of [domain](#domain) as a synonym for [VM](#vm) is specific to Xen.
Qubes diverges from this practice. See: [domain](#domain).
* The term "domU" is not a proper noun. It should follow the capitalization
rules of common nouns.
## HVM
@ -86,10 +81,13 @@ A secure compartment in Qubes OS. Currently, qubes are implemented as Xen
technology. VMs could be replaced with a different technology, and qubes would
still be called "qubes."
* **Important:** The term "qube" should be lowercase unless it is the first
word in a sentence. Note that starting a sentence with the plural of "qube"
(i.e., "Qubes...") can be ambiguous, since it may not be clear whether the
referent is a collection of qubes or [Qubes OS](#qubes-os).
* **Important:** The term "qube" is not a proper noun. It should follow the
capitalization rules of common nouns. For example, "I have three qubes" is
correct," while "I have three Qubes" is incorrect.
* Note that starting a sentence with the plural of "qube" (i.e., "Qubes...")
can be ambiguous, since it may not be clear whether the referent is a
plurality of qubes or [Qubes OS](#qubes-os).
* Example usage: "In Qubes OS, you do your banking in your 'banking' qube and
your web surfing in your 'untrusted' qube. That way, if your 'untrusted' qube
@ -106,9 +104,9 @@ security by compartmentalization (or isolation), in which activities are
compartmentalized (or isolated) in separate [qubes](#qube).
* **Important:** The official name is "Qubes OS" (note the capitalization and
the space between "Qubes" and "OS"). However, in casual conversation this is
often shortened to "Qubes." Only in technical contexts where spaces are not
permitted (e.g., usernames) may the space be omitted, as in `@QubesOS`.
the space between "Qubes" and "OS"). In casual conversation, this is often
shortened to "Qubes." Only in technical contexts where spaces are not
permitted (e.g., in usernames) may the space be omitted, as in `@QubesOS`.
## Qubes Windows Tools
@ -118,29 +116,32 @@ system. Also see [Windows](/doc/windows/).
## service qube
A [qube](#qube) the primary purpose of which is to provide a service or
A type of [qube](#qube) the primary purpose of which is to provide a service or
services to other qubes. `sys-net` and `sys-firewall` are examples of service
qubes.
## standalone
See [Standalones and HVMs](/doc/standalones-and-hvm/). A type of [qube](#qube)
that does not depend on any other qube for its root filesystem. The opposite of
an app qube. A standalone is created by cloning a template. Unlike templates,
however, standalones do not supply their root filesystems to other qubes.
See [Standalones and HVMs](/doc/standalones-and-hvm/). Any [qube](#qube) that
has its own root filesystem and does not share it with another qube.
Standalones are distinct from both templates and app qubes. A standalone is
created by cloning a template while selecting the option to make the clone
standalone.
## template
See [Templates](/doc/templates/). Any [qube](#qube) that supplies its root
filesystem to another qube. Templates are intended for installing and updating
software applications, but not for running them.
See [Templates](/doc/templates/). Any [qube](#qube) that shares its root
filesystem with another qube. A qube that is borrowing a template's root
filesystem is known as an [app qube](#app-qube) and is said to be "based on"
the template. Templates are intended for installing and updating software
applications, but not for running them.
* Since every template supplies its *own* root filesystem to at least one other
qube, no template can be based on another template. In other words, no
template is an [app qube](#app-qube).
* No template is an [app qube](#app-qube).
* Since every template supplies its *root* filesystem to at least one other
qube, no [disposable template](#disposable-template) is a template.
* A template cannot be based on another template.
* Regular templates cannot function as [disposable
templates](#disposable-template). (Disposable templates must be app qubes.)
## VM