From 0d9309ed58109c7374c58bcf3626c58378e31e26 Mon Sep 17 00:00:00 2001 From: m <3440586+maiska@users.noreply.github.com> Date: Fri, 27 Sep 2024 13:22:43 -0400 Subject: [PATCH 1/3] rst conversion omitting extra space --- user/templates/debian/debian-upgrade.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/user/templates/debian/debian-upgrade.md b/user/templates/debian/debian-upgrade.md index 12552f22..dd626566 100644 --- a/user/templates/debian/debian-upgrade.md +++ b/user/templates/debian/debian-upgrade.md @@ -189,13 +189,11 @@ instructions](https://www.debian.org/releases/buster/amd64/release-notes/ch-upgr * If sound is not working, you may need to enable the Qubes testing repository to get the testing version of `qubes-gui-agent`. This can be done by editing - the `/etc/apt/sources.list.d/qubes-r4.list` file and uncommenting the `Qubes - Updates Candidates` repo. + the `/etc/apt/sources.list.d/qubes-r4.list` file and uncommenting the `Qubes Updates Candidates` repo. * User-initiated updates/upgrades may not run when a template first starts. This is due to a new Debian config setting that attempts to update - automatically; it should be disabled with `sudo systemctl disable - apt-daily.{service,timer}`. + automatically; it should be disabled with `sudo systemctl disable apt-daily.{service,timer}`. Relevant discussions: From da85dd62d4b542f6f756183118f3c373d2918824 Mon Sep 17 00:00:00 2001 From: m <3440586+maiska@users.noreply.github.com> Date: Fri, 27 Sep 2024 13:48:11 -0400 Subject: [PATCH 2/3] from bold to italic in title for better rst conversion --- user/how-to-guides/how-to-copy-from-dom0.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/user/how-to-guides/how-to-copy-from-dom0.md b/user/how-to-guides/how-to-copy-from-dom0.md index 0aacfcbb..321bc680 100644 --- a/user/how-to-guides/how-to-copy-from-dom0.md +++ b/user/how-to-guides/how-to-copy-from-dom0.md @@ -15,7 +15,7 @@ title: How to copy from dom0 This page covers copying files and clipboard text between [dom0](/doc/glossary/#dom0) and [domUs](/doc/glossary/#domu). Since dom0 is special, the processes are different from [copying and pasting text between qubes](/doc/how-to-copy-and-paste-text/) and [copying and moving files between qubes](/doc/how-to-copy-and-move-files/). -## Copying **from** dom0 +## Copying *from* dom0 ### Copying files from dom0 @@ -61,7 +61,7 @@ In order to easily copy/paste the contents of logs from dom0 to the inter-VM cli You may now paste the log contents in qube as you normally would (e.g., Ctrl+Shift+V, then Ctrl+V). -## Copying **to** dom0 +## Copying *to* dom0 Copying anything into dom0 is not advised, since doing so can compromise the security of your Qubes system. For this reason, there is no simple means of copying anything into dom0, unlike [copying from dom0](#copying-from-dom0). From 89f81ecf82d1dcd5ee912b8b9381027be6d8ab65 Mon Sep 17 00:00:00 2001 From: qm <3440586+qm@users.noreply.github.com> Date: Fri, 4 Oct 2024 10:27:11 -0400 Subject: [PATCH 3/3] added sublists for better rst conversion formatting --- user/hardware/system-requirements.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/user/hardware/system-requirements.md b/user/hardware/system-requirements.md index ffe39f7c..63aabd50 100644 --- a/user/hardware/system-requirements.md +++ b/user/hardware/system-requirements.md @@ -122,7 +122,7 @@ We recommend consulting these resources when selecting hardware for Qubes OS: 2. The user's OEM, ODM, or MB to provide a suitable BIOS or (U)EFI update for the user's system. - Historically, AMD has often been slow to complete step (1), at least for its + - Historically, AMD has often been slow to complete step (1), at least for its client (as opposed to server) platforms. In some cases, AMD has made fixes available for its server platforms very shortly after a security embargo was lifted, but it did not make fixes available for client platforms facing the @@ -132,10 +132,10 @@ We recommend consulting these resources when selecting hardware for Qubes OS: new CPU vulnerabilities across its supported platforms very shortly after security embargoes have been lifted. - Step (2) varies by vendor. Many vendors fail to complete step (2) at all, + - Step (2) varies by vendor. Many vendors fail to complete step (2) at all, while some others take a very long time to complete it. - The bottom line is that Qubes OS **can** run on AMD systems, and the Qubes and + - The bottom line is that Qubes OS **can** run on AMD systems, and the Qubes and Xen security teams do their best to provide security support for AMD systems. However, without the ability to ship microcode updates, there is only so much they can do.