Add prompts to all code blocks with bash session

developer/debugging/automated-tests.rst

@@ -119,7 +119,7 @@ Tests are also compatible with nose2 test runner, so you can use this instead:
 
 .. code:: console
 
-      sudo systemctl stop qubesd; sudo -E nose2 -v --plugin nose2.plugins.loader.loadtests qubes.tests; sudo systemctl start qubesd
+      $ sudo systemctl stop qubesd; sudo -E nose2 -v --plugin nose2.plugins.loader.loadtests qubes.tests; sudo systemctl start qubesd
 
 
 This may be especially useful together with various nose2 plugins to store tests results (for example ``nose2.plugins.junitxml``), to ease presenting results. This is what we use on `OpenQA <https://open.qa/>`__.
@@ -140,15 +140,15 @@ Assuming you cloned the ``qubes-builder`` repository to your home directory insi
 
 .. code:: console
 
-      cd ~
-      sudo dnf install python3-pip lvm2 python35 python3-virtualenv
-      virtualenv -p /usr/bin/python35 python35
-      source python35/bin/activate
-      python3 -V
-      cd ~/qubes-builder/qubes-src/core-admin
-      pip3 install -r ci/requirements.txt
-      export PYTHONPATH=../core-qrexec:test-packages
-      ./run-tests
+      $ cd ~
+      $ sudo dnf install python3-pip lvm2 python35 python3-virtualenv
+      $ virtualenv -p /usr/bin/python35 python35
+      $ source python35/bin/activate
+      $ python3 -V
+      $ cd ~/qubes-builder/qubes-src/core-admin
+      $ pip3 install -r ci/requirements.txt
+      $ export PYTHONPATH=../core-qrexec:test-packages
+      $ ./run-tests
 
 
 To run only the tests related to e.g. ``lvm``, you may use:

developer/debugging/safe-remote-ttys.rst

@@ -70,7 +70,7 @@ If your machine has a serial console, you may with to use that, but note that a
 
 .. code:: console
 
-      script -f /dev/ttyS0
+      $ script -f /dev/ttyS0
 
 
 

developer/debugging/test-bench.rst

@@ -96,11 +96,11 @@ Internet access is intentionally disabled by default in dom0. But to ease the de
 
    .. code:: console
 
-         sudo systemctl enable sshd
-         sudo systemctl start sshd
+         $ sudo systemctl enable sshd
+         $ sudo systemctl start sshd
 
-         sudo systemctl enable dom0-network-direct
-         sudo systemctl start dom0-network-direct
+         $ sudo systemctl enable dom0-network-direct
+         $ sudo systemctl start dom0-network-direct
 
 
 
@@ -123,26 +123,26 @@ The following commands should work for you, but do keep in mind that the provisi
       # https://github.com/marmarek/openqa-tests-qubesos/blob/master/tests/update.pm
 
       # Install git
-      sudo qubes-dom0-update git || sudo dnf --setopt=reposdir=/etc/yum.repos.d install git
+      $ sudo qubes-dom0-update git || sudo dnf --setopt=reposdir=/etc/yum.repos.d install git
 
       # Download the openQA automated testing environment Salt configuration
-      git clone https://github.com/marmarek/openqa-tests-qubesos/
-      cd openqa-tests-qubesos/extra-files
-      sudo cp -a system-tests/ /srv/salt/
-      sudo qubesctl top.enable system-tests
+      $ git clone https://github.com/marmarek/openqa-tests-qubesos/
+      $ cd openqa-tests-qubesos/extra-files
+      $ sudo cp -a system-tests/ /srv/salt/
+      $ sudo qubesctl top.enable system-tests
 
       # Install the same configuration as the one in openQA
-      QUBES_VERSION=4.1
-      PILLAR_DIR=/srv/pillar/base/update
-      sudo mkdir -p $PILLAR_DIR
-      printf 'update:\n  qubes_ver: '$QUBES_VERSION'\n' | sudo tee $PILLAR_DIR/init.sls
-      printf "base:\n  '*':\n    - update\n" | sudo tee $PILLAR_DIR/init.top
-      sudo qubesctl top.enable update pillar=True
+      $ QUBES_VERSION=4.1
+      $ PILLAR_DIR=/srv/pillar/base/update
+      $ sudo mkdir -p $PILLAR_DIR
+      $ printf 'update:\n  qubes_ver: '$QUBES_VERSION'\n' | sudo tee $PILLAR_DIR/init.sls
+      $ printf "base:\n  '*':\n    - update\n" | sudo tee $PILLAR_DIR/init.top
+      $ sudo qubesctl top.enable update pillar=True
 
       # Apply states to dom0 and VMs
       # NOTE: These commands can take several minutes (if not more) without showing output
-      sudo qubesctl --show-output state.highstate
-      sudo qubesctl --max-concurrency=2 --skip-dom0 --templates --show-output state.highstate
+      $ sudo qubesctl --show-output state.highstate
+      $ sudo qubesctl --max-concurrency=2 --skip-dom0 --templates --show-output state.highstate
 
 
 Development VM