Fixes to code block pygemnt's highlighting, add __pychache__ to gitignore

add prompts to terminal sessions where needed
This commit is contained in:
qubedmaiska 2025-08-23 18:12:38 -04:00
parent 9bd5e20bfd
commit 7e76afb1a4
No known key found for this signature in database
GPG key ID: 204BCE0FD52C0501
31 changed files with 108 additions and 106 deletions

View file

@ -70,7 +70,7 @@ It helps to run the following command:
.. code:: console
nslookup security.debian.org
$ nslookup security.debian.org

View file

@ -127,7 +127,7 @@ To fix this issue:
.. code:: console
fuser -m /home
$ fuser -m /home
@ -139,9 +139,9 @@ Kill these process until they are all gone using ``kill <process ID>``.
.. code:: console
umount /home
fsck /dev/xvdb
resize2fs /dev/xvdb
$ umount /home
$ fsck /dev/xvdb
$ resize2fs /dev/xvdb

View file

@ -61,7 +61,7 @@ If this solves the problem then you will want to make the change permanent:
.. code:: console
grub2-mkconfig --output=/boot/grub2/grub.cfg
$ grub2-mkconfig --output=/boot/grub2/grub.cfg

View file

@ -13,9 +13,9 @@ To change this allocation, edit VMs kernel parameters (this is expressed in 5
.. code:: console
# qvm-prefs netvm |grep kernelopts
$ qvm-prefs netvm |grep kernelopts
kernelopts : iommu=soft swiotlb=2048 (default)
# qvm-prefs -s netvm kernelopts "iommu=soft swiotlb=8192"
$ qvm-prefs -s netvm kernelopts "iommu=soft swiotlb=8192"

View file

@ -17,7 +17,7 @@ Successfully installed in legacy mode, but had to change some xen parameters
.. code:: console
vi EFI/BOOT/grub.cfg
$ vi EFI/BOOT/grub.cfg
@ -65,7 +65,7 @@ Some Dell systems and probably others have `another bug in UEFI firmware <https:
.. code:: console
sed -i -e 's/ucode=scan/\0 efi=attr=uc/' /mnt/sysimage/boot/efi/EFI/qubes/grub.cfg
$ sed -i -e 's/ucode=scan/\0 efi=attr=uc/' /mnt/sysimage/boot/efi/EFI/qubes/grub.cfg
@ -85,7 +85,7 @@ Or if you have already rebooted after the first stage install and have encounter
.. code:: console
fdisk -l /dev/sda | grep EFI
$ fdisk -l /dev/sda | grep EFI
The output should look like this:
@ -97,14 +97,14 @@ Or if you have already rebooted after the first stage install and have encounter
.. code:: console
mkdir -p /mnt/sysimage/boot/efi
mount /dev/sda1 /mnt/sysimage/boot/efi
$ mkdir -p /mnt/sysimage/boot/efi
$ mount /dev/sda1 /mnt/sysimage/boot/efi
4. Execute:
.. code:: console
sed -i -e 's/ucode=scan/\0 efi=attr=uc/' /mnt/sysimage/boot/efi/EFI/qubes/grub.cfg
$ sed -i -e 's/ucode=scan/\0 efi=attr=uc/' /mnt/sysimage/boot/efi/EFI/qubes/grub.cfg
@ -128,7 +128,7 @@ Some firmware will not recognize the default Qubes EFI configuration. As such, i
.. code:: console
fdisk -l /dev/sda | grep EFI
$ fdisk -l /dev/sda | grep EFI
The output should look like this:
@ -140,8 +140,8 @@ Some firmware will not recognize the default Qubes EFI configuration. As such, i
.. code:: console
mkdir -p /mnt/sysimage/boot/efi
mount /dev/sda1 /mnt/sysimage/boot/efi
$ mkdir -p /mnt/sysimage/boot/efi
$ mount /dev/sda1 /mnt/sysimage/boot/efi
4. Copy ``grubx64.efi`` to the fallback path:
@ -167,7 +167,7 @@ Some firmware will not recognize the default Qubes EFI configuration. As such, i
.. code:: console
efibootmgr -v -c -u -L Qubes -l /EFI/qubes/grubx64.efi -d /dev/sda -p 1
$ efibootmgr -v -c -u -L Qubes -l /EFI/qubes/grubx64.efi -d /dev/sda -p 1

View file

@ -75,9 +75,9 @@ One solution is to add a dummy interface to allow the package to install correct
.. code:: console
ip link add d0 type dummy
ip addr add 192.168.0.1/24 dev d0
ip link set d0 up
$ ip link add d0 type dummy
$ ip addr add 192.168.0.1/24 dev d0
$ ip link set d0 up