From 98acc2c5b1bb90521c0cb073ba910c0b7036b602 Mon Sep 17 00:00:00 2001 From: Krzysztof Katowicz-Kowalewski Date: Sun, 27 Aug 2023 15:35:33 +0200 Subject: [PATCH 01/14] Update volume-backup-revert.md fixing typo: 'minimum' to 'maximum' --- user/advanced-topics/volume-backup-revert.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/user/advanced-topics/volume-backup-revert.md b/user/advanced-topics/volume-backup-revert.md index 50351107..3d836cc3 100644 --- a/user/advanced-topics/volume-backup-revert.md +++ b/user/advanced-topics/volume-backup-revert.md @@ -31,7 +31,7 @@ qvm-volume info vmname:private The output of the above command will also display the "Available revisions (for revert)" at the bottom. For a very large volume in a small pool, -revisions_to_keep should probably be set to the minimum value of 1 to minimize +revisions_to_keep should probably be set to the maximum value of 1 to minimize the possibility of the pool being accidentally filled up by snapshots. For a smaller volume for which you would like to have the future option of reverting, revisions_to_keep should probably be set to at least 2. To set From 0527252737661d8cc20f6416fedead413db9e111 Mon Sep 17 00:00:00 2001 From: Piotr Bartman-Szwarc Date: Sun, 30 Jun 2024 11:08:07 +0200 Subject: [PATCH 02/14] updater: update docs --- user/how-to-guides/how-to-update.md | 23 ++++++++++------------- 1 file changed, 10 insertions(+), 13 deletions(-) diff --git a/user/how-to-guides/how-to-update.md b/user/how-to-guides/how-to-update.md index 2462bafb..54c9bc2e 100644 --- a/user/how-to-guides/how-to-update.md +++ b/user/how-to-guides/how-to-update.md @@ -26,24 +26,26 @@ Security updates are an extremely important part of keeping your Qubes installat By default, the **Qubes Update** tool will appear as an icon in the Notification Area when updates are available. -[![Qube Updates Available](/attachment/doc/r4.0-qube-updates-available.png)](/attachment/doc/r4.0-qube-updates-available.png) +[![Qube Updates Available](/attachment/doc/r4.2-qube-updates-available.png)](/attachment/doc/r4.2-qube-updates-available.png) -However, you can also start the tool manually by selecting it in the Applications Menu under "Qubes Tools." Even if no updates have been detected, you can use this tool to check for updates manually at any time by selecting "Enable updates for qubes without known available updates," then selecting all desired items from the list and clicking "Next." +However, you can also start the tool manually by selecting it in the Applications Menu under "Qubes Tools." Even if no updates have been detected, you can use this tool to check for updates manually at any time by selecting all desired items from the list and clicking "Update". -By default, most qubes that are connected to the internet will periodically check for updates for their parent templates. If updates are available, you will receive a notification as described above. However, if you have any templates that do *not* have any online child qubes, you will *not* receive update notifications for them. Therefore, you should regularly update such templates manually instead. +By default, most qubes that are connected to the internet will periodically check for updates for their parent templates. You can check the date of the last update check in the "last checked" column. If updates are available for any qube, you will receive a notification as described above, and in the "Updates available" column you will see "YES" for that qube(s). If the update check did not find any new updates, "NO" will appear in the column. Respectively, for qubes that are no longer supported, "OBSOLETE" will be displayed. However, if you have any templates that do *not* have any online child qubes, you will *not* receive update notifications for them. By default, after a week, if updates for a given qube have not been checked, the value in the "Updates available" column will be set to "MAYBE". ## Installing updates The standard way to install updates is with the **Qubes Update** tool. (However, you can also perform the same action via the [command-line interface](#command-line-interface).) -[![Qubes Update](/attachment/doc/r4.0-software-update.png)](/attachment/doc/r4.0-software-update.png) +[![Qubes Update](/attachment/doc/r4.2-software-update.png)](/attachment/doc/r4.2-software-update.png) -Simply follow the on-screen instructions, and the tool will download and install all available updates for you. Note that if you are downloading updates over Tor (`sys-whonix`), this can take a very long time, especially if there are a lot of updates available. +You can easily decide which qubes to update by clicking on the checkbox in the column header. At startup, only the qubes for which updates are known are selected for updating, but clicking on the mentioned checkbox will also select all qubes with the "MAYBE" status. It is recommended to update all qubes with the statuses "YES" and "MAYBE". + +Then simply follow the on-screen instructions, and the tool will download and install all available updates for you. Note that if you are downloading updates over Tor (`sys-whonix`), this can take a very long time, especially if there are a lot of updates available. ## Restarting after updating @@ -53,7 +55,7 @@ Certain updates require certain components to be restarted in order for the upda - Dom0 should be restarted after all **Xen** and **kernel** updates. - On Intel systems, dom0 should be restarted after all `microcode_ctl` updates. - On AMD systems, dom0 should be restarted after all `linux-firmware` updates. -- After updating a template, first shut down the template, then restart all running qubes based on that template. +- After updating a template, first shut down the template, then restart all running qubes based on that template. The updater will try to do this for you automatically in the last step of updating. Remember to save all your data before restarting! ## AEM resealing after updating @@ -63,15 +65,10 @@ If you use [Anti Evil Maid (AEM)](/doc/anti-evil-maid/), you'll have to "reseal" -Advanced users may wish to perform updates via the command-line interface. The recommended way to do this is by applying the following two Salt states. **Applying these two Salt states is the same as updating via the Qubes Update tool.** - - - [update.qubes-dom0](/doc/salt/#updatequbes-dom0) - - [update.qubes-vm](/doc/salt/#updatequbes-vm) - -In your update qube, a terminal window opens that displays the progress of operations and output as it is logged. At the end of the process, logs are sent back to dom0. You answer any yes/no prompts in your dom0 terminal window. +Advanced users may wish to perform updates via the command-line interface. To update templates and standalones non-interactively, use the command `qubes-vm-update`, and to update dom0, use `qubes-dom0-update`. If you want to perform a more complex update, see: [update.qubes-dom0](/doc/salt/#updatequbes-dom0) and [update.qubes-vm](/doc/salt/#updatequbes-vm). Advanced users may also be interested in learning [how to enable the testing repos](/doc/testing/). From d918c03853fb2a6422f11b2ec6206a03fd669d9d Mon Sep 17 00:00:00 2001 From: Piotr Bartman-Szwarc Date: Sat, 27 Jul 2024 09:42:30 +0200 Subject: [PATCH 03/14] @andrewdavidwong comment --- user/how-to-guides/how-to-update.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/user/how-to-guides/how-to-update.md b/user/how-to-guides/how-to-update.md index 54c9bc2e..8e865234 100644 --- a/user/how-to-guides/how-to-update.md +++ b/user/how-to-guides/how-to-update.md @@ -68,7 +68,7 @@ If you use [Anti Evil Maid (AEM)](/doc/anti-evil-maid/), you'll have to "reseal" Warning: Updating with direct commands such as dnf update, and apt update is not recommended, since these bypass built-in Qubes OS update security measures. Instead, we strongly recommend using the Qubes Update tool or its command-line equivalents, as described below. (By contrast, installing packages using direct package manager commands is fine.) -Advanced users may wish to perform updates via the command-line interface. To update templates and standalones non-interactively, use the command `qubes-vm-update`, and to update dom0, use `qubes-dom0-update`. If you want to perform a more complex update, see: [update.qubes-dom0](/doc/salt/#updatequbes-dom0) and [update.qubes-vm](/doc/salt/#updatequbes-vm). +Advanced users may wish to perform updates via the command-line interface. To update templates and standalones non-interactively, use the command `qubes-vm-update`, and to update dom0, use `qubes-dom0-update`. If you want to perform an update with more advanced user-configurable options (e.g., custom pre- or post-update scripts, custom workarounds), see: [update.qubes-dom0](/doc/salt/#updatequbes-dom0) and [update.qubes-vm](/doc/salt/#updatequbes-vm). Advanced users may also be interested in learning [how to enable the testing repos](/doc/testing/). From 496a3a5ded9cbadbc9f8170cc438e9fe82af8bda Mon Sep 17 00:00:00 2001 From: Ali Mirjamali Date: Fri, 23 Aug 2024 17:43:44 +0330 Subject: [PATCH 04/14] Remove reference to `qvm-revert-template-changes` Resolves: https://github.com/QubesOS/qubes-issues/issues/6384 --- developer/system/template-implementation.md | 14 ++------------ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/developer/system/template-implementation.md b/developer/system/template-implementation.md index 4feb91fb..1bd4dd2b 100644 --- a/developer/system/template-implementation.md +++ b/developer/system/template-implementation.md @@ -73,19 +73,9 @@ When TemplateVM is stopped, the xen script moves root-cow.img to root-cow.img.ol #### Rollback template changes -There is possibility to rollback last template changes. Saved root-cow.img.old contains all changes made during last TemplateVM run. Rolling back changes is done by reverting this "binary patch". +There is possibility to rollback last template changes. Using the automatic snapshot that is normally saved every time the template is shutdown. -This is done using snapshot-merge device-mapper target (available from 2.6.34 kernel). It requires that no other snapshot device uses underlying block devices (root.img, root-cow.img via loop device). Because of this all AppVMs based on this template must be halted during this operation. - -Steps performed by **qvm-revert-template-changes**: - -1. Ensure that no other VMs uses this template. -2. Prepare snapshot device with ***root-cow.img.old*** instead of *root-cow.img* (*/etc/xen/scripts/block-snapshot prepare*). -3. Replace *snapshot* device-mapper target with *snapshot-merge*, other parameters (chunk size etc) remains untouched. Now kernel starts merging changes stored in *root-cow.img.old* into *root.img*. d-m device can be used normally (if needed). -4. Waits for merge completed: *dmsetup status* shows used snapshot blocks – it should be equal to metadata size when completed. -5. Replace *snapshot-merge* d-m target back to *snapshot*. -6. Cleanup snapshot device (if nobody uses it at the moment). -7. Move *root-cow.img.old* to *root-cow.img* (overriding existing file). +Refer to volume backup and revert [documentation](/doc/volume-backup-revert) for more information. ### Snapshot device in AppVM From 649444de0e249012ee46b18bb4f380641660f002 Mon Sep 17 00:00:00 2001 From: Randy Date: Fri, 30 Aug 2024 07:57:10 +0000 Subject: [PATCH 05/14] Update config-files.md Fix header syntax according to [the documentation guidelines](https://www.qubes-os.org/doc/documentation-style-guide/#headings) --- user/advanced-topics/config-files.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/user/advanced-topics/config-files.md b/user/advanced-topics/config-files.md index 3ffdfd55..37ee7c03 100644 --- a/user/advanced-topics/config-files.md +++ b/user/advanced-topics/config-files.md @@ -11,8 +11,7 @@ ref: 180 title: Config files --- -Qubes-specific VM config files ------------------------------- +## Qubes-specific VM config files These files are placed in `/rw`, which survives a VM restart. That way, they can be used to customize a single VM instead of all VMs based on the same template. @@ -76,8 +75,7 @@ Note that scripts need to be executable (`chmod +x`) to be used. Also, take a look at [bind-dirs](/doc/bind-dirs) for instructions on how to easily modify arbitrary system files in an app qube and have those changes persist. -GUI and audio configuration in dom0 ------------------------------------ +## GUI and audio configuration in dom0 The GUI configuration file `/etc/qubes/guid.conf` in one of a few not managed by `qubes-prefs` or the Qubes Manager tool. Sample config (included in default installation): From 35ae77260208d3bcd5e5c712068acca877120302 Mon Sep 17 00:00:00 2001 From: Randy Date: Fri, 30 Aug 2024 07:59:49 +0000 Subject: [PATCH 06/14] Update how-to-enter-fullscreen-mode.md Fix headers according to the [documentation guidelines](https://www.qubes-os.org/doc/documentation-style-guide/#headings) --- user/how-to-guides/how-to-enter-fullscreen-mode.md | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/user/how-to-guides/how-to-enter-fullscreen-mode.md b/user/how-to-guides/how-to-enter-fullscreen-mode.md index 201d6d2e..2ff92990 100644 --- a/user/how-to-guides/how-to-enter-fullscreen-mode.md +++ b/user/how-to-guides/how-to-enter-fullscreen-mode.md @@ -11,20 +11,17 @@ ref: 205 title: How to enter fullscreen mode --- -What is fullscreen mode? -------------------------- +## What is fullscreen mode? Normally, the Qubes GUI virtualization daemon restricts the VM from "owning" the full screen, ensuring that there are always clearly marked decorations drawn by the trusted Window Manager around each of the VMs window. This allows the user to easily realize to which domain a specific window belongs. See the [screenshots](/doc/QubesScreenshots/) page for examples. -Why is fullscreen mode potentially dangerous? ----------------------------------------------- +## Why is fullscreen mode potentially dangerous? If one allowed one of the VMs to "own" the full screen, e.g. to show a movie on a full screen, it might not be possible for the user to know if the applications/VM really "released" the full screen, or if it has started emulating the whole desktop and is pretending to be the trusted Window Manager, drawing shapes on the screen that look e.g. like other windows, belonging to other domains (e.g. to trick the user into entering a secret passphrase into a window that looks like belonging to some trusted domain). -Secure use of fullscreen mode ------------------------------- +## Secure use of fullscreen mode However, it is possible to deal with fullscreen mode in a secure way assuming there are mechanisms that can be used at any time to switch between windows or show the full desktop and that cannot be intercepted by the VM. The simplest example is the use of Alt+Tab for switching between windows, which is a shortcut handled by dom0. @@ -33,8 +30,7 @@ Other examples such mechanisms are the KDE "Present Windows" and "Desktop Grid" Those effects are enabled by default in KDE once Compositing gets enabled in KDE (System Settings -\> Desktop -\> Enable Desktop Effects), which is recommended anyway. By default, they are triggered by Ctrl-F8 and Ctrl-F9 key combinations, but can also be reassigned to other shortcuts. -Enabling fullscreen mode for select VMs ----------------------------------------- +## Enabling fullscreen mode for select VMs You can always put a window into fullscreen mode in Xfce4 using the trusted window manager by right-clicking on a window's title bar and selecting "Fullscreen" or pressing `alt` + `f11`. This functionality should still be considered safe, since a VM window still can't voluntarily enter fullscreen mode. From 4d98540a5e0a27ece1bb8abb5460d3ef80b69105 Mon Sep 17 00:00:00 2001 From: vysotskylev <11317846+vysotskylev@users.noreply.github.com> Date: Fri, 6 Sep 2024 20:28:34 +0200 Subject: [PATCH 07/14] Fix typo in how-to-install-software.md --- user/how-to-guides/how-to-install-software.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/user/how-to-guides/how-to-install-software.md b/user/how-to-guides/how-to-install-software.md index da7aae0e..be3ee664 100644 --- a/user/how-to-guides/how-to-install-software.md +++ b/user/how-to-guides/how-to-install-software.md @@ -429,7 +429,7 @@ these in an app qube you need to take the following steps: When the install is complete you can close the terminal window. 3. Refresh the Applications list for the app qube. In the Qubes Menu for the - **app qube*** launch the Qube Settings. Then go to the Applications tab and + **app qube** launch the Qube Settings. Then go to the Applications tab and click "Refresh Applications" The refresh will take a few minutes; after it's complete the Snap app will From dd93bd2d56917ea8e5f6ceb919cd9ea49b175b75 Mon Sep 17 00:00:00 2001 From: Matthew <944951+Chiramisu@users.noreply.github.com> Date: Fri, 4 Oct 2024 23:29:05 -0700 Subject: [PATCH 08/14] Fixes broken link to Xen Project Overview in intro.md --- introduction/intro.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/introduction/intro.md b/introduction/intro.md index 142d4095..a9089ea6 100644 --- a/introduction/intro.md +++ b/introduction/intro.md @@ -19,7 +19,7 @@ title: Introduction

Qubes OS is a free and open-source, security-oriented operating system for single-user desktop computing. Qubes OS leverages - + Xen-based virtualization to allow for the creation and management of isolated compartments called qubes.

From c263b40758a4b0bbd6792d054e88d1961faf10b9 Mon Sep 17 00:00:00 2001 From: Marnix Croes <93143998+MarnixCroes@users.noreply.github.com> Date: Thu, 10 Oct 2024 13:46:53 +0200 Subject: [PATCH 09/14] fix link to section --- user/hardware/system-requirements.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/user/hardware/system-requirements.md b/user/hardware/system-requirements.md index ffe39f7c..6512dd53 100644 --- a/user/hardware/system-requirements.md +++ b/user/hardware/system-requirements.md @@ -37,9 +37,9 @@ title: System requirements - [Intel VT-x](https://en.wikipedia.org/wiki/X86_virtualization#Intel_virtualization_.28VT-x.29) with [EPT](https://en.wikipedia.org/wiki/Second_Level_Address_Translation#Extended_Page_Tables) - [Intel VT-d](https://en.wikipedia.org/wiki/X86_virtualization#Intel-VT-d) - For security, we recommend processors that are recent enough to still be - receiving microcode updates (see [below](#important-updates) for details). + receiving microcode updates (see [below](#important-notes) for details). - AMD processors are not recommended due to inconsistent security support on - client platforms (see [below](#important-updates) for details). + client platforms (see [below](#important-notes) for details). - **Memory:** 16 GB RAM From 6b21fa65f3976b1df59b6780d2330a2052e46ad7 Mon Sep 17 00:00:00 2001 From: Ali Mirjamali Date: Sun, 27 Oct 2024 15:57:04 +0330 Subject: [PATCH 10/14] Document global clipboard for GUI protocol 1.8 According to: https://github.com/QubesOS/qubes-gui-daemon/pull/150#issuecomment-2431883322 According to: https://github.com/QubesOS/qubes-gui-daemon/pull/150#issuecomment-2432486669 --- developer/system/gui.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/developer/system/gui.md b/developer/system/gui.md index dfd04801..6de31dc7 100644 --- a/developer/system/gui.md +++ b/developer/system/gui.md @@ -90,9 +90,10 @@ Clipboard sharing implementation Certainly, it would be insecure to allow AppVM to read/write the clipboards of other AppVMs unconditionally. Therefore, the following mechanism is used: -- there is a "qubes clipboard" in dom0 - its contents are stored in a regular file in dom0. +- there is a "qubes clipboard" in dom0 - its contents are stored in a regular file in dom0 as `/run/qubes/qubes-clipboard.bin`. - if the user wants to copy local AppVM clipboard to qubes clipboard, she must focus on any window belonging to this AppVM, and press **Ctrl-Shift-C**. This combination is trapped by `qubes-guid`, and `CLIPBOARD_REQ` message is sent to AppVM. `qubes-gui` responds with `CLIPBOARD_DATA` message followed by clipboard contents. - the user focuses on other AppVM window, presses **Ctrl-Shift-V**. This combination is trapped by `qubes-guid`, and `CLIPBOARD_DATA` message followed by qubes clipboard contents is sent to AppVM; `qubes-gui` copies data to the local clipboard, and then user can paste its contents to local applications normally. +- a supplementary JSON metadata file will be saved as `/run/qubes/qubes-clipboard.bin.metadata` on global clipboard copy or paste actions. Explanation of each field is available in `xside.h` header file of `qubes-guid` under `clipboard_metadata` structure. While the output from `qubes-guid` is fully JSON compatible, the `qubes-guid` parser is limited. It expects line breaks after each key-value pair and only one key-value pair per line. Opening and closing curly braces should be on their own lines. There should be no leading white-space. This way, the user can quickly copy clipboards between AppVMs. This action is fully controlled by the user, it cannot be triggered/forced by any AppVM. From eea342bdb0e10097f3d00fc670ee7e1135f3fa74 Mon Sep 17 00:00:00 2001 From: Piotr Bartman-Szwarc Date: Tue, 12 Nov 2024 13:05:49 +0100 Subject: [PATCH 11/14] migration to fido2: proxy setup clarification to avoid confusing errors solves QubesOS/qubes-issues/issues/9064 --- user/security-in-qubes/ctap-proxy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/user/security-in-qubes/ctap-proxy.md b/user/security-in-qubes/ctap-proxy.md index 92e127dc..4c858532 100644 --- a/user/security-in-qubes/ctap-proxy.md +++ b/user/security-in-qubes/ctap-proxy.md @@ -85,7 +85,7 @@ $ sudo qubes-dom0-update qubes-ctap-dom0 $ qvm-service --enable work qubes-ctap-proxy ``` -The above assumes a `work` qube in which you would like to enable ctap. Repeat the `qvm-service` command for all qubes that should have the proxy enabled. Alternatively, you can add `qubes-ctap-proxy` in VM settings -> Services in the Qube Manager of each qube you would like to enable the service. +The above assumes a `work` qube in which you would like to enable ctap. Repeat the `qvm-service` command for all qubes that should have the client proxy enabled. Alternatively, you can add `qubes-ctap-proxy` in VM settings -> Services in the Qube Manager of each qube you would like to enable the service. Attempting to start the `qubes-ctap-proxy` service in the device-hosting qube (`sys-usb`) will fail. In Fedora templates: From a2d0d042dce2c6dde7fde901851e11af9461ded5 Mon Sep 17 00:00:00 2001 From: kennethrrosen Date: Sat, 30 Nov 2024 11:34:26 +0000 Subject: [PATCH 12/14] Add standalone timeout note Note standalone `qrexec_timeout` workaround QubesOS/qubes-issues/issues/9251 --- user/advanced-topics/resize-disk-image.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/user/advanced-topics/resize-disk-image.md b/user/advanced-topics/resize-disk-image.md index b7805bd2..c06eaa1b 100644 --- a/user/advanced-topics/resize-disk-image.md +++ b/user/advanced-topics/resize-disk-image.md @@ -32,7 +32,8 @@ In most cases, the GUI tool Qube Settings (available for every qube from the Sta ![vm-settings-disk-image.png](/attachment/doc/r4.0-vm-settings-disk-image.png) -In case of standalone qubes and templates, just change the Disk Storage settings above. +In case of standalone qubes and templates, just change the Disk Storage settings above. If the standalone fails to start, temporarily increase the `qrexec_timeout`, [as described here](https://github.com/QubesOS/qubes-issues/issues/9251#issuecomment-2121596415). + In case of template-based qubes, the private storage (the /home directory and user files) can be changed in the qube's own settings, but the system root image is [inherited from the template](/doc/getting-started/), and so it must be changed in the template settings. If you are increasing the disk image size for Linux-based qubes installed from Qubes OS repositories in Qubes 4.0 or later, changing the settings above is all you need to do - in other cases, you may need to do more, according to instructions below. See also the OS-specific follow-up instructions below. From 47f23eda45a61ffcda186b580c9e18c741ab5f09 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sol=C3=A8ne=20Rapenne?= Date: Tue, 21 Jan 2025 19:56:49 +0100 Subject: [PATCH 13/14] fix: broken anchor --- introduction/issue-tracking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/introduction/issue-tracking.md b/introduction/issue-tracking.md index 46c038fd..5326e698 100644 --- a/introduction/issue-tracking.md +++ b/introduction/issue-tracking.md @@ -41,7 +41,7 @@ Great! Thank you for taking the time and effort to help improve Qubes! To ensure 1. Carefully read our issue tracking [guidelines](#guidelines). If your issue would violate any of the guidelines, **stop**. Please do not submit it. 2. [Search through the existing issues](#search-tips), both open and closed, to see if your issue already exists. If it does, **stop**. [Do not open a duplicate.](/doc/issue-tracking/#new-issues-should-not-be-duplicates-of-existing-issues) Instead, comment on the existing issue. 3. Go [here](https://github.com/QubesOS/qubes-issues/issues/new/choose). - 4. Select the [type](#type) of issue you want to open. + 4. Select the [type](#types) of issue you want to open. 5. Enter a descriptive title. 6. Do not delete the provided issue template. Fill out every applicable section. 7. Make sure to mention any relevant documentation and other issues you've already seen. We don't know what you've seen unless you tell us. If you don't list it, we'll assume you haven't seen it. From f58574bca78af8c7a3ff338049e513b170be26ba Mon Sep 17 00:00:00 2001 From: Ali Mirjamali Date: Sat, 31 Aug 2024 14:51:21 +0330 Subject: [PATCH 14/14] Add instructions on resuming partial downloads Resolves: https://github.com/QubesOS/qubes-issues/issues/8563 Adding simple instructions on resuming downloads with for users with unsteady Internet connections who are unfamiliar with wget. --- user/downloading-installing-upgrading/installation-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/user/downloading-installing-upgrading/installation-guide.md b/user/downloading-installing-upgrading/installation-guide.md index c38cbc35..a4684667 100644 --- a/user/downloading-installing-upgrading/installation-guide.md +++ b/user/downloading-installing-upgrading/installation-guide.md @@ -43,7 +43,7 @@ Even on supported hardware, you must ensure that [IOMMU-based virtualization](ht ### Copying the ISO onto the installation medium -Pick the most secure existing computer and OS you have available for downloading and copying the Qubes ISO onto the installation medium. [Download](/downloads/) a Qubes ISO. +Pick the most secure existing computer and OS you have available for downloading and copying the Qubes ISO onto the installation medium. [Download](/downloads/) a Qubes ISO. If your Internet connection is unstable and the download is interrupted, you could resume the partial download with `wget --continue` in case you are currently using wget for downloading or use a download-manager with resume capability. Alternatively you can download installation ISO via BitTorrent that sometimes enables higher download speeds and more reliable downloads of large files.