minor formatting, wording

This commit is contained in:
qubedmaiska 2025-03-21 18:38:35 -04:00
parent 7e2b1b1858
commit 0c274977fe
No known key found for this signature in database
GPG key ID: 204BCE0FD52C0501
3 changed files with 34 additions and 31 deletions

View file

@ -110,7 +110,8 @@ binds=( "${binds[@]/'/var/lib/tor'}" )
## Custom persist feature ##
Custom persist is an optional advanced feature allowing the creation of minimal state AppVM. The purpose of such an AppVM is to avoid unwanted data to persist as much as possible by the disabling the ability to configure persistence from the VM itself. When enabled, the following happens:
Custom persist is an optional advanced feature allowing the creation of minimal state AppVM. The purpose of such an AppVM is to avoid unwanted data to persist as much as possible by disabling the ability to configure persistence from the VM itself. When enabled, the following happens:
* ``/rw/config/rc.local`` is no longer executed
* ``/rw/config/qubes-firewall-user-script`` is ignored
* ``/rw/config/suspend-module-blacklist`` is ignored

View file

@ -17,13 +17,13 @@ shutdown. (Note that this is a different, lower level activity than the
In Qubes, when you create a new VM, it's volumes are stored in one of the
system's [Storage Pools](/doc/storage-pools/). On pool creation, a
revisions_to_keep default value is set for the entire pool. (For a pool creation
`revisions_to_keep` default value is set for the entire pool. (For a pool creation
example, see [Storing app qubes on Secondary Drives](/doc/secondary-storage/).)
Thereafter, each volume associated with a VM that is stored in this pool
inherits the pool default revisions_to_keep.
inherits the pool default `revisions_to_keep`.
For the private volume associated with a VM named vmname, you may inspect the
value of revisions_to_keep from the dom0 CLI as follows:
For the private volume associated with a VM named *vmname*, you may inspect the
value of `revisions_to_keep` from the dom0 CLI as follows:
```
qvm-volume info vmname:private
@ -31,11 +31,11 @@ qvm-volume info vmname:private
The output of the above command will also display the "Available revisions
(for revert)" at the bottom. For a very large volume in a small pool,
revisions_to_keep should probably be set to the maximum value of 1 to minimize
`revisions_to_keep` should probably be set to the maximum value of 1 to minimize
the possibility of the pool being accidentally filled up by snapshots. For a
smaller volume for which you would like to have the future option of reverting,
revisions_to_keep should probably be set to at least 2. To set
revisions_to_keep for this same VM / volume example:
`revisions_to_keep` should probably be set to at least 2. To set
`revisions_to_keep` for this same VM / volume example:
```
qvm-volume config vmname:private revisions_to_keep 2