mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-12-16 00:03:51 -05:00
Clarify definitions
This commit is contained in:
parent
325abc8cc3
commit
b3c61ed5c0
1 changed files with 48 additions and 47 deletions
|
|
@ -12,64 +12,59 @@ title: Glossary
|
||||||
|
|
||||||
## app qube
|
## 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.
|
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
|
* Historical note: This term originally meant "a qube intended for running user
|
||||||
software applications" (hence the name "app").
|
software applications" (hence the name "app").
|
||||||
|
|
||||||
* Historical note: This is the preferred term replacing the deprecated term
|
|
||||||
"TemplateBasedVM."
|
|
||||||
|
|
||||||
## disposable
|
## disposable
|
||||||
|
|
||||||
See [How to Use Dispoables](/doc/how-to-use-disposables/). A temporary [app
|
See [How to Use Dispoables](/doc/how-to-use-disposables/). A type of temporary
|
||||||
qube](#app-qube) based on a [disposable template](#disposable-template) that
|
[app qube](#app-qube) that can quickly be created, used, and destroyed. Each
|
||||||
can quickly be created, used, and destroyed.
|
disposable is based on a [disposable template](#disposable-template).
|
||||||
|
|
||||||
## disposable template
|
## disposable template
|
||||||
|
|
||||||
A type of [app qube](#app-qube) on which [disposables](#disposable) are based.
|
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
|
(Not to be confused with the concept of a regular [template](#template) that is
|
||||||
disposable, which does not exist in Qubes OS.)
|
itself disposable, which does not exist in Qubes OS.)
|
||||||
|
|
||||||
Disposable templates are not [templates](#template), since (being app qubes)
|
* Disposable templates must be app qubes. They cannot be regular
|
||||||
they do not have root filesystems of their own to provide to other qubes.
|
[templates](#template).
|
||||||
Rather, disposable templates are complementary to templates insofar as
|
|
||||||
disposable templates provide their own user filesystems to the disposables
|
* Each [disposables](#disposable) is based on a disposable template, which is
|
||||||
based on them.
|
in turn based on a regular [templates](#template).
|
||||||
|
|
||||||
## dom0
|
## 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
|
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
|
toolstack and has special privileges relative to other domains, such as direct
|
||||||
access to most hardware.
|
access to most hardware.
|
||||||
|
|
||||||
* The term "dom0" is not a proper noun and should not be capitalized unless
|
* The term "dom0" is not a proper noun. It should follow the capitalization
|
||||||
it's the first word in a sentence.
|
rules of common nouns.
|
||||||
|
|
||||||
* The use of [domain](#domain) as a synonym for [VM](#vm) is specific to Xen.
|
|
||||||
Qubes diverges from this practice. See: [domain](#domain).
|
|
||||||
|
|
||||||
## domain
|
## domain
|
||||||
|
|
||||||
_This term is deprecated in the context of Qubes OS._
|
|
||||||
|
|
||||||
In Xen, a synonym for [VM](#vm). See ["domain" on the Xen
|
In Xen, a synonym for [VM](#vm). See ["domain" on the Xen
|
||||||
Wiki](https://wiki.xenproject.org/wiki/Domain).
|
Wiki](https://wiki.xenproject.org/wiki/Domain).
|
||||||
|
|
||||||
|
* This term has no official meaning in the context of Qubes OS.
|
||||||
|
|
||||||
## domU
|
## domU
|
||||||
|
|
||||||
Unprivileged [domain](#domain). Also known as **guest** domains, domUs are the
|
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
|
counterparts to dom0. In Xen, all VMs except dom0 are domUs. By default, most
|
||||||
domUs lack direct hardware access.
|
domUs lack direct hardware access.
|
||||||
|
|
||||||
* The term "domU" is not a proper noun and should not be capitalized unless it
|
* The term "domU" is not a proper noun. It should follow the capitalization
|
||||||
is the first word in a sentence.
|
rules of common nouns.
|
||||||
|
|
||||||
* The use of [domain](#domain) as a synonym for [VM](#vm) is specific to Xen.
|
|
||||||
Qubes diverges from this practice. See: [domain](#domain).
|
|
||||||
|
|
||||||
## HVM
|
## 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
|
technology. VMs could be replaced with a different technology, and qubes would
|
||||||
still be called "qubes."
|
still be called "qubes."
|
||||||
|
|
||||||
* **Important:** The term "qube" should be lowercase unless it is the first
|
* **Important:** The term "qube" is not a proper noun. It should follow the
|
||||||
word in a sentence. Note that starting a sentence with the plural of "qube"
|
capitalization rules of common nouns. For example, "I have three qubes" is
|
||||||
(i.e., "Qubes...") can be ambiguous, since it may not be clear whether the
|
correct," while "I have three Qubes" is incorrect.
|
||||||
referent is a collection of qubes or [Qubes OS](#qubes-os).
|
|
||||||
|
* 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
|
* 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
|
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).
|
compartmentalized (or isolated) in separate [qubes](#qube).
|
||||||
|
|
||||||
* **Important:** The official name is "Qubes OS" (note the capitalization and
|
* **Important:** The official name is "Qubes OS" (note the capitalization and
|
||||||
the space between "Qubes" and "OS"). However, in casual conversation this is
|
the space between "Qubes" and "OS"). In casual conversation, this is often
|
||||||
often shortened to "Qubes." Only in technical contexts where spaces are not
|
shortened to "Qubes." Only in technical contexts where spaces are not
|
||||||
permitted (e.g., usernames) may the space be omitted, as in `@QubesOS`.
|
permitted (e.g., in usernames) may the space be omitted, as in `@QubesOS`.
|
||||||
|
|
||||||
## Qubes Windows Tools
|
## Qubes Windows Tools
|
||||||
|
|
||||||
|
|
@ -118,29 +116,32 @@ system. Also see [Windows](/doc/windows/).
|
||||||
|
|
||||||
## service qube
|
## 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
|
services to other qubes. `sys-net` and `sys-firewall` are examples of service
|
||||||
qubes.
|
qubes.
|
||||||
|
|
||||||
## standalone
|
## standalone
|
||||||
|
|
||||||
See [Standalones and HVMs](/doc/standalones-and-hvm/). A type of [qube](#qube)
|
See [Standalones and HVMs](/doc/standalones-and-hvm/). Any [qube](#qube) that
|
||||||
that does not depend on any other qube for its root filesystem. The opposite of
|
has its own root filesystem and does not share it with another qube.
|
||||||
an app qube. A standalone is created by cloning a template. Unlike templates,
|
Standalones are distinct from both templates and app qubes. A standalone is
|
||||||
however, standalones do not supply their root filesystems to other qubes.
|
created by cloning a template while selecting the option to make the clone
|
||||||
|
standalone.
|
||||||
|
|
||||||
## template
|
## template
|
||||||
|
|
||||||
See [Templates](/doc/templates/). Any [qube](#qube) that supplies its root
|
See [Templates](/doc/templates/). Any [qube](#qube) that shares its root
|
||||||
filesystem to another qube. Templates are intended for installing and updating
|
filesystem with another qube. A qube that is borrowing a template's root
|
||||||
software applications, but not for running them.
|
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
|
* No template is an [app qube](#app-qube).
|
||||||
qube, no template can be based on another template. In other words, no
|
|
||||||
template is an [app qube](#app-qube).
|
|
||||||
|
|
||||||
* Since every template supplies its *root* filesystem to at least one other
|
* A template cannot be based on another template.
|
||||||
qube, no [disposable template](#disposable-template) is a template.
|
|
||||||
|
* Regular templates cannot function as [disposable
|
||||||
|
templates](#disposable-template). (Disposable templates must be app qubes.)
|
||||||
|
|
||||||
## VM
|
## VM
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue