Accurately categorize DVM Template in Qubes Manager

[mfc]

receiving feedback from new user attempting to customize their DispVM and not realizing that *-dvm is a template, because it is listed as an AppVM. Or somehow make it more clear to users not to run programs in it.

I understand it is technically dependent on another template, but it is also problematic for a new user.

[marmarek]

*-dvm is not a TemplateVM. It is not a place where you install applications (https://www.qubes-os.org/doc/glossary/#templatevm).

But indeed it may require some clarification, because it also isn't the place to use for work.

-- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?

[mfc]

yeah, maybe a new category (different icon, etc)?

[andrewdavidwong]

See the discussion in #2486. We already have a term for this now: DVM Template. I'll add a further explanation to that entry.

[andrewdavidwong]

Ok, I see that this isn't purely a documentation issue. It is, strictly speaking, inaccurate for Qubes Manager to categorize a DVM Template as an AppVM, since we define AppVMs as VMs that are intended for running software applications (which DVM Templates are not). However, as @marmarek pointed out, DVM Templates are also not intended for installing software (which is how we define TemplateVMs). As I pointed out in #2486, they're somewhere in-between, so @mfc is probably correct that there should exist a new category.

[andrewdavidwong]

In Qubes 4.0, the situation has changed. AppVMs can now be DVM Templates. I've updated the glossary to reflect this: https://github.com/QubesOS/qubes-doc/commit/82f50fe2e0dab972d7e028ee5232ecdf2cf3680d