mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-08-06 13:44:22 -04:00
Various minor fixes
* Remove sphinx warnings * Add true warning directive * Use console lexer instead of bash if appropriate
This commit is contained in:
parent
71038b7928
commit
af14439c9a
5 changed files with 12 additions and 13 deletions
|
@ -107,7 +107,7 @@ Next, set the old ``sys-firewall`` autostart to false, and update any references
|
||||||
|
|
||||||
To create one with a PCI device attached such as for ``sys-net`` or ``sys-usb``, use the additional commands as follows.
|
To create one with a PCI device attached such as for ``sys-net`` or ``sys-usb``, use the additional commands as follows.
|
||||||
|
|
||||||
**Note:** You can use ``qvm-pci`` to :ref:`determine <user/how-to-guides/how-to-use-pci-devices:\`\`qvm-pci\`\` usage>` the ``<BDF>``. Also, you will often need to include the ``-o no-strict-reset=True`` :ref:`option <user/how-to-guides/how-to-use-pci-devices:no-strict-reset>` with USB controllers.
|
**Note:** You can use ``qvm-pci`` to :ref:`determine <user/how-to-guides/how-to-use-pci-devices:\`\`qvm-pci\`\` usage>` the ``<BDF>``. Also, you will often need to include the ``-o no-strict-reset=True`` :option:`no-strict-reset` option with USB controllers.
|
||||||
|
|
||||||
.. code:: bash
|
.. code:: bash
|
||||||
|
|
||||||
|
|
|
@ -11,7 +11,7 @@ Automatic Method
|
||||||
|
|
||||||
First, copy any files that you wish to keep from the template’s ``/home`` and ``/rw`` folders to a safe storage location. Then, in a dom0 terminal, run:
|
First, copy any files that you wish to keep from the template’s ``/home`` and ``/rw`` folders to a safe storage location. Then, in a dom0 terminal, run:
|
||||||
|
|
||||||
.. code:: bash
|
.. code:: console
|
||||||
|
|
||||||
$ sudo qubes-dom0-update --action=reinstall qubes-template-package-name
|
$ sudo qubes-dom0-update --action=reinstall qubes-template-package-name
|
||||||
|
|
||||||
|
@ -23,7 +23,7 @@ Note that Qubes may initially refuse to perform the reinstall if the exact revis
|
||||||
|
|
||||||
**Reminder:** If you’re trying to reinstall a template that is not in an enabled repo, you must enable that repo. For example:
|
**Reminder:** If you’re trying to reinstall a template that is not in an enabled repo, you must enable that repo. For example:
|
||||||
|
|
||||||
.. code:: bash
|
.. code:: console
|
||||||
|
|
||||||
$ sudo qubes-dom0-update --enablerepo=qubes-templates-community --action=reinstall qubes-template-whonix-ws
|
$ sudo qubes-dom0-update --enablerepo=qubes-templates-community --action=reinstall qubes-template-whonix-ws
|
||||||
|
|
||||||
|
@ -51,14 +51,14 @@ In what follows, the term “target template” refers to whichever template you
|
||||||
|
|
||||||
3. Uninstall the target template from dom0:
|
3. Uninstall the target template from dom0:
|
||||||
|
|
||||||
.. code:: bash
|
.. code:: console
|
||||||
|
|
||||||
$ sudo dnf remove <template-package-name>
|
$ sudo dnf remove <template-package-name>
|
||||||
|
|
||||||
|
|
||||||
For example, to uninstall the ``whonix-gw`` template:
|
For example, to uninstall the ``whonix-gw`` template:
|
||||||
|
|
||||||
.. code:: bash
|
.. code:: console
|
||||||
|
|
||||||
$ sudo dnf remove qubes-template-whonix-gw
|
$ sudo dnf remove qubes-template-whonix-gw
|
||||||
|
|
||||||
|
@ -66,14 +66,14 @@ In what follows, the term “target template” refers to whichever template you
|
||||||
|
|
||||||
4. Reinstall the target template in dom0:
|
4. Reinstall the target template in dom0:
|
||||||
|
|
||||||
.. code:: bash
|
.. code:: console
|
||||||
|
|
||||||
$ sudo qubes-dom0-update --enablerepo=<optional-additional-repo> \
|
$ sudo qubes-dom0-update --enablerepo=<optional-additional-repo> \
|
||||||
<template-package-name>
|
<template-package-name>
|
||||||
|
|
||||||
For example, to install the ``whonix-gw`` template:
|
For example, to install the ``whonix-gw`` template:
|
||||||
|
|
||||||
.. code:: bash
|
.. code:: console
|
||||||
|
|
||||||
$ sudo qubes-dom0-update --enablerepo=qubes-templates-community \
|
$ sudo qubes-dom0-update --enablerepo=qubes-templates-community \
|
||||||
qubes-template-whonix-gw
|
qubes-template-whonix-gw
|
||||||
|
|
|
@ -235,4 +235,4 @@ Customizing disposables
|
||||||
You can change the template used to generate the disposables, and change settings used in the disposable savefile. These changes will be reflected in every new disposable based on that template. Full instructions can be found :doc:`here </user/advanced-topics/disposable-customization>`.
|
You can change the template used to generate the disposables, and change settings used in the disposable savefile. These changes will be reflected in every new disposable based on that template. Full instructions can be found :doc:`here </user/advanced-topics/disposable-customization>`.
|
||||||
|
|
||||||
.. |disposablevm-example.png| image:: /attachment/doc/disposablevm-example.png
|
.. |disposablevm-example.png| image:: /attachment/doc/disposablevm-example.png
|
||||||
|
|
||||||
|
|
|
@ -2,7 +2,6 @@
|
||||||
How to use optical discs
|
How to use optical discs
|
||||||
========================
|
========================
|
||||||
|
|
||||||
|
|
||||||
Passthrough reading and recording (a.k.a., “burning”) are not supported by Qubes OS. This is not a limitation of Xen, which provides scsiback and scsifront drivers, but of Qubes OS. It will be fixed in the future.
|
Passthrough reading and recording (a.k.a., “burning”) are not supported by Qubes OS. This is not a limitation of Xen, which provides scsiback and scsifront drivers, but of Qubes OS. It will be fixed in the future.
|
||||||
|
|
||||||
Currently, the only options for reading and recording optical discs (e.g., CDs, DVDs, BRDs) in Qubes are:
|
Currently, the only options for reading and recording optical discs (e.g., CDs, DVDs, BRDs) in Qubes are:
|
||||||
|
@ -11,8 +10,8 @@ Currently, the only options for reading and recording optical discs (e.g., CDs,
|
||||||
|
|
||||||
2. Attach a SATA optical drive to a secondary SATA controller, then assign this secondary SATA controller to a VM.
|
2. Attach a SATA optical drive to a secondary SATA controller, then assign this secondary SATA controller to a VM.
|
||||||
|
|
||||||
3. Use a SATA optical drive attached to dom0. (**Caution:** This option is `potentially dangerous <https://forum.qubes-os.org/t/19075#dom0-precautions>`__.)
|
3. Use a SATA optical drive attached to dom0.
|
||||||
|
|
||||||
|
.. warning:: This option is `potentially dangerous <https://forum.qubes-os.org/t/19075#dom0-precautions>`__.
|
||||||
|
|
||||||
|
To access an optical disc via USB follow the :ref:`typical procedure for attaching a USB device <attaching-and-detaching-a-usb-device>`, then check with the **Qubes Devices** widget to see what device in the target qube the USB optical drive was attached to. Typically this would be ``sr0``. For example, if ``sys-usb`` has device ``3-2`` attached to the ``work`` qube’s ``sr0``, you would mount it with ``mount /dev/sr0 /mnt/removable``. You could also write to a disc with ``wodim -v dev=/dev/sr0 -eject /home/user/Qubes.iso``.
|
||||||
To access an optical disc via USB follow the :ref:`typical procedure for attaching a USB device <user/how-to-guides/how-to-use-usb-devices:with the command line tool>`, then check with the **Qubes Devices** widget to see what device in the target qube the USB optical drive was attached to. Typically this would be ``sr0``. For example, if ``sys-usb`` has device ``3-2`` attached to the ``work`` qube’s ``sr0``, you would mount it with ``mount /dev/sr0 /mnt/removable``. You could also write to a disc with ``wodim -v dev=/dev/sr0 -eject /home/user/Qubes.iso``.
|
|
||||||
|
|
|
@ -71,7 +71,7 @@ By installing these templates, you are trusting not only the Qubes developers an
|
||||||
|
|
||||||
- :doc:`Gentoo Minimal </user/templates/minimal-templates>`
|
- :doc:`Gentoo Minimal </user/templates/minimal-templates>`
|
||||||
|
|
||||||
- :doc:`CentOS* <https://forum.qubes-os.org/t/19006>`
|
- `CentOS* <https://forum.qubes-os.org/t/19006>`__
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue