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

Remove obsolete prompts, extract session comments to instructions

Browse source
This commit is contained in:
qubedmaiska 2025-08-16 09:17:57 -04:00
parent 2d2bcb06a6
commit f96169ba0e
No known key found for this signature in database
GPG key ID: 204BCE0FD52C0501
3 changed files with 26 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

10
project-security/verifying-signatures.rst
View file

@ -426,11 +426,11 @@ Download both the ISO and its signature file. Put both of them in the same direc
.. code:: console .. code:: console
$ gpg2 -v --verify Qubes-RX-x86_64.iso.asc Qubes-RX-x86_64.iso $ gpg2 -v --verify Qubes-RX-x86_64.iso.asc Qubes-RX-x86_64.iso
$ gpg: armor header: Version: GnuPG v1 gpg: armor header: Version: GnuPG v1
$ gpg: Signature made <TIME> using RSA key ID 03FA5082 gpg: Signature made <TIME> using RSA key ID 03FA5082
$ gpg: using PGP trust model gpg: using PGP trust model
$ gpg: Good signature from "Qubes OS Release X Signing Key" gpg: Good signature from "Qubes OS Release X Signing Key"
$ gpg: binary signature, digest algorithm SHA256 gpg: binary signature, digest algorithm SHA256
This is just an example, so the output you receive will not look exactly the same. What matters is the line that says ``Good signature from "Qubes OS Release X Signing Key"``. This confirms that the signature on the ISO is good. This is just an example, so the output you receive will not look exactly the same. What matters is the line that says ``Good signature from "Qubes OS Release X Signing Key"``. This confirms that the signature on the ISO is good.

13
user/advanced-topics/secondary-storage.rst
View file

@ -54,13 +54,10 @@ First, collect some information in a dom0 terminal:
$ sudo lvs $ sudo lvs
Take note of the VG and thin pool names for your second drive., then register it with Qubes: Take note of the VG and thin pool names for your second drive, then register it with Qubes, where ``<pool_name>`` is a freely chosen pool name, ``<vg_name>`` is LVM volume group name and ``<thin_pool_name>`` is LVM thin pool name:
.. code:: console .. code:: console
# <pool_name> is a freely chosen pool name
# <vg_name> is LVM volume group name
# <thin_pool_name> is LVM thin pool name
$ qvm-pool --add <pool_name> lvm_thin -o volume_group=<vg_name>,thin_pool=<thin_pool_name>,revisions_to_keep=2 $ qvm-pool --add <pool_name> lvm_thin -o volume_group=<vg_name>,thin_pool=<thin_pool_name>,revisions_to_keep=2
@ -79,12 +76,10 @@ It is possible to use an existing Btrfs storage if it is configured. In dom0, av
btrfs show filesystem btrfs show filesystem
To register the storage to qubes: To register the storage to qubes use the following command where ``<pool_name>`` is a freely chosen pool name adn ``<dir_path>`` is the mounted path to the second btrfs storage:
.. code:: console .. code:: console
# <pool_name> is a freely chosen pool name
# <dir_path> is the mounted path to the second btrfs storage
$ qvm-pool --add <pool_name> file-reflink -o dir_path=<dir_path>,revisions_to_keep=2 $ qvm-pool --add <pool_name> file-reflink -o dir_path=<dir_path>,revisions_to_keep=2
@ -206,12 +201,10 @@ Unmount the temporary Btrfs filesystem:
$ rmdir /mnt/new_qube_storage $ rmdir /mnt/new_qube_storage
Mount the subvolume with compression enabled if desired: Mount the subvolume with compression enabled if desired, where ``<compression>`` can take the values ``zlib|lzo|zstd``. ``<subvol>`` is a btrfs subvolume "qubes" in this example.
.. code:: console .. code:: console
# <compression> zlib|lzo|zstd
# <subvol> btrfs subvolume "qubes" in this example
$ sudo mount /dev/mapper/luks-b20975aa-8318-433d-8508-6c23982c6cde /var/lib/qubes_newpool -o compress=<compression>,subvol=qubes $ sudo mount /dev/mapper/luks-b20975aa-8318-433d-8508-6c23982c6cde /var/lib/qubes_newpool -o compress=<compression>,subvol=qubes

22
user/templates/windows/windows-qubes-4-0.rst
View file

@ -144,7 +144,6 @@ An unofficial, third-party tool for automating this process is available `here <
Summary Summary
^^^^^^^ ^^^^^^^
.. code:: console .. code:: console
$ qvm-create --class StandaloneVM --label red --property virt_mode=hvm win7new $ qvm-create --class StandaloneVM --label red --property virt_mode=hvm win7new
@ -155,14 +154,29 @@ Summary
$ qvm-prefs win7new debug true $ qvm-prefs win7new debug true
$ qvm-features win7new video-model cirrus $ qvm-features win7new video-model cirrus
$ qvm-start --cdrom=untrusted:/home/user/windows_install.iso win7new $ qvm-start --cdrom=untrusted:/home/user/windows_install.iso win7new
# restart after the first part of the windows installation process ends
Restart after the first part of the windows installation process ends:
.. code:: console
$ qvm-start win7new $ qvm-start win7new
# once Windows is installed and working
Once Windows is installed and working:
.. code:: console
$ qvm-prefs win7new memory 2048 $ qvm-prefs win7new memory 2048
$ qvm-prefs win7new maxmem 2048 $ qvm-prefs win7new maxmem 2048
$ qvm-features --unset win7new video-model $ qvm-features --unset win7new video-model
$ qvm-prefs win7new qrexec_timeout 300 $ qvm-prefs win7new qrexec_timeout 300
# with Qubes Windows Tools installed:
With Qubes Windows Tools installed:
.. code:: console
$ qvm-prefs win7new debug false $ qvm-prefs win7new debug false