mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-08-14 01:16:02 -04:00
small formatting fixes in markdown
This commit is contained in:
parent
e7385e96b5
commit
2d3bfcb39f
5 changed files with 5 additions and 11 deletions
|
@ -14,7 +14,7 @@ title: Firewall
|
|||
Introduction
|
||||
----------------------------------
|
||||
This page explains use of the firewall in Qubes 4.2, using `nftables`.
|
||||
In Qubes 4.1, all firewall components used `iptables`. For details of that usage see [here](../firewall_4.1/)
|
||||
In Qubes 4.1, all firewall components used `iptables`. For details of that usage see [here](../firewall_4.1/).
|
||||
|
||||
|
||||
Understanding firewalling in Qubes
|
||||
|
|
|
@ -121,11 +121,7 @@ The same general procedure may be used to upgrade any template based on the stan
|
|||
|
||||
If this attempt is successful, proceed to step 4.
|
||||
|
||||
* `dnf` may complain:
|
||||
|
||||
`
|
||||
At least X MB more space needed on the / filesystem.
|
||||
`
|
||||
* `dnf` may complain: `At least X MB more space needed on the / filesystem.`
|
||||
|
||||
In this case, one option is to [resize the template's disk image](/doc/resize-disk-image/) before reattempting the upgrade process.
|
||||
(See [Additional Information](#additional-information) below for other options.)
|
||||
|
|
|
@ -26,9 +26,7 @@ Similarly, while working, the XScreenSaver dialog may pop up (indicating the scr
|
|||
|
||||
If you are experiencing the any of the above symptoms, try disabling the window compositor:
|
||||
|
||||
`
|
||||
Q → System Tools → Window Manager Tweaks → Compositor → uncheck “Enable display compositing”
|
||||
`
|
||||
`Q → System Tools → Window Manager Tweaks → Compositor → uncheck “Enable display compositing”`
|
||||
|
||||
## Post installation, screen goes black and freezes following LUKS decryption
|
||||
|
||||
|
|
|
@ -62,7 +62,7 @@ qvm-prefs <HVMname> kernel ""
|
|||
|
||||
## HVM crashes when booting from ISO
|
||||
|
||||
If your HVM crashes when trying to boot an ISO, first ensure that ` qvm-prefs <HVMname> kernel` is empty, as shown above.
|
||||
If your HVM crashes when trying to boot an ISO, first ensure that `qvm-prefs <HVMname> kernel` is empty, as shown above.
|
||||
If this doesn't help, then disable memory balancing and set the minimum memory to 2GB.
|
||||
|
||||
You can disable memory-balancing in the settings, under the “Advanced” tab.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue