Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-02-17 21:34:17 -05:00
Code Issues Packages Projects Releases Wiki Activity

security-guidelines 4.0 update

Browse Source 
yum -> dnf
Replace R3.x specific description of treatment of template's home directory with link to /doc/template
This commit is contained in:
awokd 2018-02-01 14:59:45 +00:00 committed by GitHub
parent fb7952840e
commit 922340303e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
security/security-guidelines.md
View File

@ -32,7 +32,7 @@ See the page on [Verifying Signatures](https://www.qubes-os.org/security/verifyi
Once you have Qubes installed, the standard program installation command for Fedora and Qubes repositories Once you have Qubes installed, the standard program installation command for Fedora and Qubes repositories
~~~ ~~~
sudo yum install <program> sudo dnf install <program>
~~~ ~~~
automatically accomplishes this verification. automatically accomplishes this verification.
@ -93,7 +93,7 @@ sudo qubes-dom0-update
and run in templates and standalone VM and run in templates and standalone VM
~~~ ~~~
sudo yum update sudo dnf update
~~~ ~~~
or use the equivalent items in Qubes Manager, which displays an icon when an update is available. or use the equivalent items in Qubes Manager, which displays an icon when an update is available.
@ -154,12 +154,6 @@ As explained [here](/getting-started/#appvms-qubes-and-templatevms), dom0 should
TemplateBasedVM Directories TemplateBasedVM Directories
--------------------------- ---------------------------
* Whenever a TemplateBasedVM is created, the contents of its `/home`
directory is copied from its parent TemplateVM. From that point onward, the child TemplateBasedVM's `/home`
is independent from its parent TemplateVM's `/home`, which means that any
subsequent changes to the parent TemplateVM's `/home` will no longer affect
the child TemplateBasedVM's `/home`.
* Once a TemplateBasedVM has been created, any changes in its `/home`, * Once a TemplateBasedVM has been created, any changes in its `/home`,
`/usr/local`, or `/rw/config` directories will be persistent across reboots, `/usr/local`, or `/rw/config` directories will be persistent across reboots,
which means that any files stored there will still be available after which means that any files stored there will still be available after
@ -167,3 +161,6 @@ TemplateBasedVM Directories
TemplateBasedVMs persist in this manner. If you would like to make changes TemplateBasedVMs persist in this manner. If you would like to make changes
in other directories which *do* persist in this manner, you must make those in other directories which *do* persist in this manner, you must make those
changes in the parent TemplateVM. changes in the parent TemplateVM.
* See [here](/doc/templates) for more detail and version specific information.