mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-08-21 12:48:21 -04:00
Use console lexer instead of bash with a prompt
This commit is contained in:
parulin
parent
ba609d123e
commit
b53776e1eb
49 changed files with 256 additions and 256 deletions
|
|
@ -27,7 +27,7 @@ With the command-line interface
|
|||
|
||||
To update the list of available applications, use the ``qvm-sync-appmenus`` command in dom0, replacing ``<QUBE_NAME>`` by the qube name:
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
$ qvm-sync-appmenus <QUBE_NAME>
|
||||
|
||||
|
|
@ -35,7 +35,7 @@ To update the list of available applications, use the ``qvm-sync-appmenus`` comm
|
|||
|
||||
When using the *Refresh Applications* button in a qube’s settings, the command ``qvm-sync-appmenus`` is used at least one time. When refreshing an AppVM application, it is also run against the template. So the console equivalent of clicking the *Refresh button* is the following (always in dom0):
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
$ qvm-sync-appmenus <APPVM_NAME>
|
||||
$ qvm-sync-appmenus <TEMPLATE_NAME>
|
||||
|
|
@ -44,7 +44,7 @@ When using the *Refresh Applications* button in a qube’s settings, the command
|
|||
|
||||
In dom0, the ``qvm-appmenus`` tool allows the user to see the list of available applications (unstable feature), the whitelist of currently show application (unstable feature) and to change this list:
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
$ qvm-appmenus --set-whitelist <FILE_PATH> <QUBE_NAME>
|
||||
|
||||
|
|
@ -152,7 +152,7 @@ What if a removed application is still in the app menu?
|
|||
|
||||
First, try this in dom0:
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
$ qvm-appmenus --update --force <QUBE_NAME>
|
||||
|
||||
|
|
@ -160,7 +160,7 @@ First, try this in dom0:
|
|||
|
||||
You can also try:
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
$ qvm-appmenus --remove <QUBE_NAME>
|
||||
|
||||
|
|
@ -186,7 +186,7 @@ The line starting with ``Exec=`` points out the exact command run by dom0 to sta
|
|||
|
||||
It’s possible to run the command to check the output, by copying this line without ``Exec=``, and remove ``-q`` (quiet option). But it could be more useful to run it in the qube, with the ``qubes.StartApp`` service:
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
$ /etc/qubes-rpc/qubes.StartApp <APPLICATION_NAME>
|
||||
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The above steps applies to old VM disks format. These steps may work on Qubes 4.
|
|||
|
||||
For example:
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
$ sudo lvs
|
||||
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ There are a variety of other problems that could arise when using a USB installa
|
|||
|
||||
This error message is related to the faulty creation of the USB installation medium. If you receive this error message during installation, please make sure you have followed the instructions on :ref:`how to write your ISO to a USB key <user/downloading-installing-upgrading/installation-guide:copying the iso onto the installation medium>`. Specifically, the ``dd`` command listed on that page has been verified to solve this issue on multiple Qubes installation versions.
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
$ sudo dd if=Qubes-RX-x86_64.iso of=/dev/sdY status=progress bs=1048576 && sync
|
||||
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ First, determine which kernel module corresponds to your wireless card. There ar
|
|||
|
||||
The easiest is via the output of ``lspci -k`` in your sys-net VM:
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
[user@sys-net ~]$ lspci -k
|
||||
00:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
|
||||
|
|
@ -64,7 +64,7 @@ You can check which drivers are currently loaded with ``lsmod``, and view detail
|
|||
|
||||
For example, we list what modules we have loaded:
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
[user@sys-net ~]$ lsmod
|
||||
Module Size Used by
|
||||
|
|
@ -78,7 +78,7 @@ For example, we list what modules we have loaded:
|
|||
|
||||
and check one:
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
[user@sys-net ~]$ modinfo iwlmvm | grep -E '^(description|author|depends):'
|
||||
author: Copyright(c) 2003- 2015 Intel Corporation <ilw@linux.intel.com>
|
||||
|
|
@ -91,7 +91,7 @@ Hey, it’s our wireless driver!
|
|||
|
||||
Now, check if reloading the module makes wireless work again:
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
[user@sys-net ~]$ sudo rmmod iwlmvm
|
||||
[user@sys-net ~]$ sudo modprobe iwlmvm
|
||||
|
|
@ -102,7 +102,7 @@ and try reconnecting to a network that is known to work.
|
|||
|
||||
If that is successful, see below about having Qubes automatically reload the driver for you. If not, try also reloading some dependent modules, in our example we must also reload iwlwifi:
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
[user@sys-net ~]$ modinfo iwlwifi | grep -E '^(description|author|depends):'
|
||||
author: Copyright(c) 2003- 2015 Intel Corporation <ilw@linux.intel.com>
|
||||
|
|
@ -111,7 +111,7 @@ If that is successful, see below about having Qubes automatically reload the dri
|
|||
|
||||
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
[user@sys-net ~]$ sudo rmmod iwlmvm
|
||||
[user@sys-net ~]$ sudo rmmod iwlwifi
|
||||
|
|
@ -128,7 +128,7 @@ If reloading the driver (which resets the hardware into a known-state) resolves
|
|||
|
||||
In the above example, it would look like this:
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
[user@sys-net config]$ cat /rw/config/suspend-module-blacklist
|
||||
# You can list here modules you want to be unloaded before going to sleep. This
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ When a template is marked as ‘installed by package manager’, but cannot be u
|
|||
|
||||
1. Check the state of ``installed_by_rpm``
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
$ qvm-prefs template-vm-name
|
||||
|
||||
|
|
@ -41,7 +41,7 @@ When a template is marked as ‘installed by package manager’, but cannot be u
|
|||
|
||||
2. If ``installed_by_rpm - True``, mark the template as not installed by package manager
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
$ qvm-prefs template-vm-name installed_by_rpm false
|
||||
|
||||
|
|
@ -53,7 +53,7 @@ When a template is marked as ‘installed by package manager’, but cannot be u
|
|||
|
||||
- If ``installed_by_rpm - False``, remove the template like you would a regular qube:
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
$ qvm-remove template-vm-name
|
||||
|
||||
|
|
@ -95,7 +95,7 @@ If the error occurs as a result of too little initial memory, increase the initi
|
|||
|
||||
For example:
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
[user@dom0 ~]$ sudo qubes-dom0-update --enablerepo=qubes-templates-itl qubes-template-debian-10
|
||||
Using sys-whonix as UpdateVM to download updates for Dom0; this may take some time...
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue