From 72b9e24fb4b0d3e7327beb575fcdf7bb4b85ca89 Mon Sep 17 00:00:00 2001 From: Andrew David Wong Date: Sat, 25 Feb 2017 17:54:41 -0800 Subject: [PATCH] Explain intended use of DVM Templates QubesOS/qubes-issues#2651 --- reference/glossary.md | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/reference/glossary.md b/reference/glossary.md index 1b80173d..7fec416f 100644 --- a/reference/glossary.md +++ b/reference/glossary.md @@ -137,9 +137,15 @@ An abbreviation of [DispVM](#dispvm), typically used to refer to DVM Template ------------ -The TemplateVM on which [DispVMs](#dispvm) are based. By default, a VM named -`fedora-XX-dvm` is created on most Qubes installations (where `XX` is the -current Fedora version). +TemplateBasedVMs on which [DispVMs](#dispvm) are based. By default, a +DVM Template named `fedora-XX-dvm` is created on most Qubes installations +(where `XX` is the Fedora version of the default TemplateVM). DVM Templates are +neither [TemplateVMs](#templatevm) nor [AppVMs](#appvm). They are intended +neither for installing nor running software. Rather, they are intended for +*customizing* or *configuring* software that has already been installed on the +TemplateVM on which the DVM Template is based (see [DispVM Customization]). This +software is then intended to be run (in its customized stated) in DispVMs that +are based on the DVM Template. PV -- @@ -190,3 +196,6 @@ for disk and network I/O, thus providing PV-like (or better) performance on HVM systems. This allows for optimal performance on guest operating systems such as Windows. + +[DispVM Customization]: /doc/dispvm-customization/ +