diff --git a/developer/building/development-workflow.md b/developer/building/development-workflow.md index 53646679..ecfc2030 100644 --- a/developer/building/development-workflow.md +++ b/developer/building/development-workflow.md @@ -10,7 +10,6 @@ ref: 66 title: Development Workflow --- - A workflow for developing Qubes OS+ First things first, setup [QubesBuilder](/doc/qubes-builder/). This guide @@ -537,4 +536,3 @@ Usage: add this line to `/etc/apt/sources.list` on test machine (adjust host and ~~~ deb http://local-test.lan/linux-deb/r3.1 jessie-unstable main ~~~ - diff --git a/developer/building/qubes-builder-details.md b/developer/building/qubes-builder-details.md index d6fdb259..8b5c8c8a 100644 --- a/developer/building/qubes-builder-details.md +++ b/developer/building/qubes-builder-details.md @@ -10,7 +10,6 @@ ref: 65 title: Qubes Builder Details --- - Components Makefile.builder file -------------------------------- diff --git a/developer/building/qubes-iso-building.md b/developer/building/qubes-iso-building.md index 0455e6e6..f30b7b26 100644 --- a/developer/building/qubes-iso-building.md +++ b/developer/building/qubes-iso-building.md @@ -12,7 +12,6 @@ ref: 63 title: Qubes ISO Building --- - Build Environment ----------------- diff --git a/developer/code/code-signing.md b/developer/code/code-signing.md index 09492c2b..236c6aac 100644 --- a/developer/code/code-signing.md +++ b/developer/code/code-signing.md @@ -6,7 +6,6 @@ ref: 51 title: Code Signing --- - All contributions to the Qubes OS [source code](/doc/source-code/) must be cryptographically signed by the author's PGP key. ## Generating a Key @@ -202,4 +201,3 @@ Please upload it. If you're submitting a patch by emailing the [developer mailing list](/support/#qubes-devel), simply sign your email with your PGP key. One good way to do this is with a program like [Enigmail](https://www.enigmail.net/). Enigmail is a security addon for the Mozilla Thunderbird email client that allows you to easily digitally encrypt and sign your emails. - diff --git a/developer/code/coding-style.md b/developer/code/coding-style.md index ac7fdf23..4f2013c5 100644 --- a/developer/code/coding-style.md +++ b/developer/code/coding-style.md @@ -11,7 +11,6 @@ ref: 53 title: Coding Style --- - Rationale --------- diff --git a/developer/code/license.md b/developer/code/license.md index 91325bf4..a2550e78 100644 --- a/developer/code/license.md +++ b/developer/code/license.md @@ -10,7 +10,6 @@ ref: 52 title: Software License --- - Qubes is a compilation of software packages, each under its own license. The compilation is made available under the GNU General Public License version 2. The full text of the GPL v2 license can be found [here](https://www.gnu.org/licenses/gpl-2.0.html). diff --git a/developer/code/source-code.md b/developer/code/source-code.md index 05ee47d0..7098ace7 100644 --- a/developer/code/source-code.md +++ b/developer/code/source-code.md @@ -10,7 +10,6 @@ ref: 54 title: Source Code --- - All the Qubes code is kept in Git repositories. We have divided the project into several components, each of which has its own separate repository, for example: @@ -81,4 +80,3 @@ method you choose, you must [sign your code](/doc/code-signing/) before it can b name and email, so that *your* name will be used as a commit's author. 5. Send your patch to `qubes-devel`. Start the message subject with `[PATCH]`. - diff --git a/developer/debugging/automated-tests.md b/developer/debugging/automated-tests.md index aaf13e01..e4a7e674 100644 --- a/developer/debugging/automated-tests.md +++ b/developer/debugging/automated-tests.md @@ -9,7 +9,6 @@ ref: 45 title: Automated Tests --- - ## Unit and Integration Tests Starting with Qubes R3 we use [python unittest](https://docs.python.org/3/library/unittest.html) to perform automatic tests of Qubes OS. @@ -260,4 +259,3 @@ In practice, however, either Xen or QEMU crashes when this is attempted. Nonetheless, PV works well, which is sufficient for automated installation testing. Thanks to an anonymous donor, our openQA system is hosted in a datacenter on hardware that meets these requirements. - diff --git a/developer/debugging/mount-lvm-image.md b/developer/debugging/mount-lvm-image.md index 74597578..d484b5a7 100644 --- a/developer/debugging/mount-lvm-image.md +++ b/developer/debugging/mount-lvm-image.md @@ -6,7 +6,6 @@ ref: 46 title: How to Mount LVM Images --- - You want to read your LVM image (e.g., there is a problem where you can't start any VMs except dom0). 1: make the image available for qubesdb. @@ -53,4 +52,3 @@ From the GUI, or from the command line: # References Please consult this issue's [comment](https://github.com/QubesOS/qubes-issues/issues/4687#issuecomment-451626625). - diff --git a/developer/debugging/profiling.md b/developer/debugging/profiling.md index 71ff9010..230351de 100644 --- a/developer/debugging/profiling.md +++ b/developer/debugging/profiling.md @@ -10,7 +10,6 @@ ref: 48 title: Python Profiling --- - This is a python profiling primer. For the purpose of this document, `qubes-dev` is name of the domain used for postprocessing profiling stats. diff --git a/developer/debugging/safe-remote-ttys.md b/developer/debugging/safe-remote-ttys.md index 89286b7f..bd71d96c 100644 --- a/developer/debugging/safe-remote-ttys.md +++ b/developer/debugging/safe-remote-ttys.md @@ -8,7 +8,6 @@ ref: 49 title: Safe Remote Dom0 Terminals --- - If you do not have working graphics in Dom0, then using a terminal can be quite annoying! This was the case for the author while trying to debug PCI-passthrough of a machine's primary (only) GPU. diff --git a/developer/debugging/test-bench.md b/developer/debugging/test-bench.md index bc21ea3f..7f07a745 100644 --- a/developer/debugging/test-bench.md +++ b/developer/debugging/test-bench.md @@ -10,7 +10,6 @@ ref: 44 title: How to Set Up a Test Bench --- - This guide shows how to set up simple test bench that automatically test your code you're about to push. It is written especially for `core3` branch of `core-admin.git` repo, but some ideas are universal. We will set up a spare machine (bare metal, not a virtual) that will be hosting our experimental Dom0. We will communicate with it via Ethernet and SSH. This tutorial assumes you are familiar with [QubesBuilder](/doc/qubes-builder/) and you have it set up and running flawlessly. diff --git a/developer/debugging/vm-interface.md b/developer/debugging/vm-interface.md index 5d7e6492..741e52c7 100644 --- a/developer/debugging/vm-interface.md +++ b/developer/debugging/vm-interface.md @@ -11,7 +11,6 @@ ref: 47 title: VM Configuration Interface --- - Qubes VM have some settings set by dom0 based on VM settings. There are multiple configuration channels, which includes: - QubesDB diff --git a/developer/debugging/windows-debugging.md b/developer/debugging/windows-debugging.md index 8ab71f11..cc81c2c4 100644 --- a/developer/debugging/windows-debugging.md +++ b/developer/debugging/windows-debugging.md @@ -10,7 +10,6 @@ ref: 50 title: Windows Debugging --- - Debugging Windows code can be tricky in a virtualized environment. The guide below assumes Xen hypervisor and Windows 7 VMs. User-mode debugging is usually straightforward if it can be done on one machine. Just duplicate your normal debugging environment in the VM. diff --git a/developer/general/doc-guidelines.md b/developer/general/doc-guidelines.md index 2eb883e0..628a7b99 100644 --- a/developer/general/doc-guidelines.md +++ b/developer/general/doc-guidelines.md @@ -561,4 +561,3 @@ Here's an example that follows the indentation rules: Please try to write good commit messages, according to the [instructions in our coding style guidelines](/doc/coding-style/#commit-message-guidelines). - diff --git a/developer/general/gsoc.md b/developer/general/gsoc.md index 2fc7b34d..c99e5580 100644 --- a/developer/general/gsoc.md +++ b/developer/general/gsoc.md @@ -586,4 +586,3 @@ would override all the user changes there). More details: ---- We adapted some of the language here about GSoC from the [KDE GSoC page](https://community.kde.org/GSoC). - diff --git a/developer/general/gsod.md b/developer/general/gsod.md index 7998b640..76e40c76 100644 --- a/developer/general/gsod.md +++ b/developer/general/gsod.md @@ -6,7 +6,6 @@ ref: 242 title: Google Season of Docs --- - Thank you for your interest in participating in the [2021 Google Season of Docs](https://developers.google.com/season-of-docs/) program with the [Qubes OS team](/team/). You can read more about the Google Season of Docs in the official [guides](https://developers.google.com/season-of-docs/docs/) and [FAQ](https://developers.google.com/season-of-docs/docs/faq). ## 2021 Project Idea @@ -145,4 +144,3 @@ Fixing this last point may require very close cooperation with developers, as th - [Markdown](https://daringfireball.net/projects/markdown/) **Mentor**: [Marek Marczykowski-Górecki](/team/) - diff --git a/developer/general/package-contributions.md b/developer/general/package-contributions.md index 0b45862c..c15cae1a 100644 --- a/developer/general/package-contributions.md +++ b/developer/general/package-contributions.md @@ -6,7 +6,6 @@ ref: 29 title: Package Contributions --- - _This page is for developers who wish to contribute packages. If you want to install contributed packages, please see [installing contributed packages](/doc/installing-contributed-packages/)._ @@ -101,4 +100,3 @@ As the maintainer of the package, it is your privilege and responsibility to: If you do not wish to be the maintainer of your package, please let us know. If you do not act on your maintainer duties for a given package for an extended period of time and after at least one reminder, we will assume that you no longer wish to be the maintainer for that package. - diff --git a/developer/general/usability-ux.md b/developer/general/usability-ux.md index 21232299..75748bcc 100644 --- a/developer/general/usability-ux.md +++ b/developer/general/usability-ux.md @@ -6,7 +6,6 @@ ref: 31 title: Usability & UX --- - Software that is too complicated to use, is often unused. Because we want as many people as possible to benefit from its unique security properties, the usability and user experience of Qubes OS is an utmost priority! We ask anyone developing for Qubes OS to please read through this guide to better understand the user experience we strive to achieve. We also ask them to review [our style guide](/doc/style-guide/) for other design related information. diff --git a/developer/releases/1_0/release-notes.md b/developer/releases/1_0/release-notes.md index 4f46a77c..9681a3e6 100644 --- a/developer/releases/1_0/release-notes.md +++ b/developer/releases/1_0/release-notes.md @@ -8,7 +8,6 @@ ref: 18 title: Qubes R1.0 Release Notes --- - Detailed release notes in [this blog post](https://blog.invisiblethings.org/2012/09/03/introducing-qubes-10.html). ## Known issues diff --git a/developer/releases/2_0/release-notes.md b/developer/releases/2_0/release-notes.md index 09d95953..a6e30028 100644 --- a/developer/releases/2_0/release-notes.md +++ b/developer/releases/2_0/release-notes.md @@ -8,7 +8,6 @@ ref: 25 title: Qubes R2.0 Release Notes --- - Detailed release notes in [this blog post](https://blog.invisiblethings.org/2014/09/26/announcing-qubes-os-release-2.html) ## New features since 1.0 diff --git a/developer/releases/3_0/schedule.md b/developer/releases/3_0/schedule.md index 30111df5..512ee3ab 100644 --- a/developer/releases/3_0/schedule.md +++ b/developer/releases/3_0/schedule.md @@ -8,7 +8,6 @@ ref: 20 title: Qubes R3.0 Release Schedule --- - | Date | Stage | | -----------:| ------------------------------------- | | 5 Sep 2015 | current-testing freeze before 3.0-rc3 | diff --git a/developer/releases/3_1/release-notes.md b/developer/releases/3_1/release-notes.md index 1b0bafcd..35d1bcd4 100644 --- a/developer/releases/3_1/release-notes.md +++ b/developer/releases/3_1/release-notes.md @@ -6,7 +6,6 @@ ref: 16 title: Qubes R3.1 release notes --- - ## New features since 3.0 * Management Stack based of Salt Stack in dom0 - [documentation](/doc/salt/) @@ -64,4 +63,3 @@ for migrating of all of the user VMs. Alternatively you can [upgrade to R3.0 using](/doc/releases/3.0/release-notes/#upgrading) first, then follow the instructions above. This will be time consuming process. - diff --git a/developer/releases/3_1/schedule.md b/developer/releases/3_1/schedule.md index dda8869d..14481818 100644 --- a/developer/releases/3_1/schedule.md +++ b/developer/releases/3_1/schedule.md @@ -8,7 +8,6 @@ ref: 17 title: Qubes R3.1 Release Schedule --- - This schedule is based on [Version Scheme](/doc/version-scheme/#release-schedule). | Date | Stage | diff --git a/developer/releases/3_2/release-notes.md b/developer/releases/3_2/release-notes.md index 37eca329..547dff27 100644 --- a/developer/releases/3_2/release-notes.md +++ b/developer/releases/3_2/release-notes.md @@ -6,7 +6,6 @@ ref: 21 title: Qubes R3.2 release notes --- - ## New features since 3.1 * Management Stack extended to support in-VM configuration - [documentation](/doc/salt/) @@ -60,4 +59,3 @@ for migrating of all of the user VMs. Alternatively you can [upgrade to R3.1 using](/doc/releases/3.1/release-notes/#upgrading) first, then follow the instructions above. This will be time consuming process. - diff --git a/developer/releases/3_2/schedule.md b/developer/releases/3_2/schedule.md index 945fefa6..ed769eec 100644 --- a/developer/releases/3_2/schedule.md +++ b/developer/releases/3_2/schedule.md @@ -8,7 +8,6 @@ ref: 22 title: Qubes R3.2 Release Schedule --- - This schedule is based on [Version Scheme](/doc/version-scheme/#release-schedule). | Date | Stage | diff --git a/developer/releases/4_0/release-notes.md b/developer/releases/4_0/release-notes.md index b2ed70e6..b80a1959 100644 --- a/developer/releases/4_0/release-notes.md +++ b/developer/releases/4_0/release-notes.md @@ -6,7 +6,6 @@ ref: 23 title: Qubes R4.0 release notes --- - New features since 3.2 ---------------------- @@ -106,4 +105,3 @@ There is no in-place upgrade path from earlier Qubes versions. The only supported option to upgrade to Qubes R4.0 is to install it from scratch and use [qubes backup and restore tools](/doc/backup-restore/) for migrating of all of the user VMs. We also provide [detailed instruction](/doc/upgrade-to-r4.0/) for this procedure. - diff --git a/developer/releases/4_0/schedule.md b/developer/releases/4_0/schedule.md index fb8035fb..98d4c1df 100644 --- a/developer/releases/4_0/schedule.md +++ b/developer/releases/4_0/schedule.md @@ -8,7 +8,6 @@ ref: 24 title: Qubes R4.0 Release Schedule --- - This schedule is based on [Version Scheme](/doc/version-scheme/#release-schedule). | Date | Stage | diff --git a/developer/releases/notes.md b/developer/releases/notes.md index 71c1bd2c..8059bf69 100644 --- a/developer/releases/notes.md +++ b/developer/releases/notes.md @@ -6,7 +6,6 @@ ref: 13 title: Release Notes --- - * [Qubes R1.0 release notes](/doc/releases/1.0/release-notes/) * [Qubes R2.0 release notes](/doc/releases/2.0/release-notes/) * [Qubes R3.0 release notes](/doc/releases/3.0/release-notes/) diff --git a/developer/releases/schedules.md b/developer/releases/schedules.md index afcd82e9..d2af2d6e 100644 --- a/developer/releases/schedules.md +++ b/developer/releases/schedules.md @@ -6,7 +6,6 @@ ref: 15 title: Release Schedules --- - * [Qubes R3.0 release schedule](/doc/releases/3.0/schedule/) * [Qubes R3.1 release schedule](/doc/releases/3.1/schedule/) * [Qubes R3.2 release schedule](/doc/releases/3.2/schedule/) diff --git a/developer/releases/todo.md b/developer/releases/todo.md index d3144959..98179d89 100644 --- a/developer/releases/todo.md +++ b/developer/releases/todo.md @@ -8,7 +8,6 @@ ref: 14 title: Release Checklist --- - *the checklist is probably unfinished* On -rc1 diff --git a/developer/releases/version-scheme.md b/developer/releases/version-scheme.md index 9c131892..da4ccf04 100644 --- a/developer/releases/version-scheme.md +++ b/developer/releases/version-scheme.md @@ -10,7 +10,6 @@ ref: 151 title: Version Scheme --- - Beginning with R3 release, we change (and formalise) the versioning scheme. From now on, it will be as follows. @@ -155,4 +154,3 @@ Check installed version If you want to know which version you are running, for example to report an issue, you can either check in the Qubes Manager menu under About / Qubes OS or in the file /etc/qubes-release in dom0. For the latter you can use a command like `cat /etc/qubes-release` in a dom0 terminal. - diff --git a/developer/services/admin-api.md b/developer/services/admin-api.md index 38ddc9d0..03678282 100644 --- a/developer/services/admin-api.md +++ b/developer/services/admin-api.md @@ -274,4 +274,3 @@ In addition, there is a mechanism to prevent concurrent modifications of the pol `qrexec-client-vm` - diff --git a/developer/services/dom0-secure-updates.md b/developer/services/dom0-secure-updates.md index 9a167969..b4f1bdb8 100644 --- a/developer/services/dom0-secure-updates.md +++ b/developer/services/dom0-secure-updates.md @@ -10,7 +10,6 @@ ref: 43 title: Dom0 Secure Updates --- - Reasons for Dom0 updates ------------------------ diff --git a/developer/services/qrexec-internals.md b/developer/services/qrexec-internals.md index dc4e5a3f..b31dbd94 100644 --- a/developer/services/qrexec-internals.md +++ b/developer/services/qrexec-internals.md @@ -11,7 +11,6 @@ ref: 39 title: 'Qrexec: Qubes RPC Internals' --- - (*This page details the current implementation of qrexec (qrexec3). A [general introduction](/doc/qrexec/) to qrexec is also available. For the implementation of qrexec2, see [here](/doc/qrexec2/#qubes-rpc-internals).*) diff --git a/developer/services/qrexec-socket-services.md b/developer/services/qrexec-socket-services.md index fcef05a9..a3d47a09 100644 --- a/developer/services/qrexec-socket-services.md +++ b/developer/services/qrexec-socket-services.md @@ -6,7 +6,6 @@ ref: 42 title: 'Qrexec: Socket-based Services' --- - *This page describes how to implement and use new socket-backed services for qrexec. See [qrexec](/doc/qrexec/) for general overview of the qrexec framework.* As of Qubes 4.1, qrexec allows implementing services not only as executable files, but also as Unix sockets. diff --git a/developer/system/audio.md b/developer/system/audio.md index 0aa98b75..e5abe774 100644 --- a/developer/system/audio.md +++ b/developer/system/audio.md @@ -6,7 +6,6 @@ ref: 60 title: Audio Virtualization --- - VMs on Qubes OS have access to virtualized audio through the PulseAudio module. It consists of two parts: diff --git a/developer/system/networking.md b/developer/system/networking.md index a5e564d0..76a88de4 100644 --- a/developer/system/networking.md +++ b/developer/system/networking.md @@ -11,7 +11,6 @@ ref: 59 title: Networking --- - ## Overall description In Qubes, the standard Xen networking is used, based on backend driver in the driver domain and frontend drivers in VMs. In order to eliminate layer 2 attacks originating from a compromised VM, routed networking is used instead of the default bridging of `vif` devices and NAT is applied at each network hop. The default *vif-route* script had some deficiencies (requires `eth0` device to be up, and sets some redundant iptables rules), therefore the custom *vif-route-qubes* script is used. diff --git a/developer/system/security-critical-code.md b/developer/system/security-critical-code.md index b4a585d6..21f075cb 100644 --- a/developer/system/security-critical-code.md +++ b/developer/system/security-critical-code.md @@ -11,7 +11,6 @@ ref: 55 title: Security-critical Code --- - Below is a list of security-critical (i.e., trusted) code components in Qubes OS. A successful attack against any of these components could compromise the system's security. This code can be thought of as the Trusted Computing Base (TCB) of Qubes OS. @@ -69,4 +68,3 @@ This means that we must trust at least some of the vendors that supply the code (We don't have to trust *all* of them, but we at least have to trust the few that provide the apps we use in the most critical domains.) In practice, we trust the software provided by the [Fedora Project](https://getfedora.org/). This software is signed by Fedora distribution keys, so it is also critical that the tools used in domains for software updates (`dnf` and `rpm`) are trustworthy. - diff --git a/developer/system/security-design-goals.md b/developer/system/security-design-goals.md index 8806723c..41b1a2a6 100644 --- a/developer/system/security-design-goals.md +++ b/developer/system/security-design-goals.md @@ -12,7 +12,6 @@ ref: 210 title: Security Design Goals --- - Qubes OS implements a security-by-isolation (or security-by-compartmentalization) approach by providing the ability to easily create many security domains. These domains are implemented as lightweight Virtual Machines (VMs) running under the Xen hypervisor. Qubes' main objective is to provide strong isolation between these domains, so that even if an attacker compromises one of the domains, the others are still safe. Qubes, however, does not attempt to provide any security isolation for applications running within the same domain. For example, a buggy web browser running in a Qubes domain could still be compromised just as easily as on a regular Linux distribution. The difference that Qubes makes is that now the attacker doesn't have access to all the software running in the other domains. Qubes also provides features that make it easy and convenient to run these multiple domains, such as seamless GUI integration into one common desktop, secure clipboard copy and paste between domains, secure file transfer between domains, disposable VMs, and much more. Qubes also provides an advanced networking infrastructure that allows for the creation of multiple network VMs which isolate all the world-facing networking stacks and proxy VMs which can be used for advanced VPN configurations and tunneling over untrusted connections. diff --git a/developer/system/storage-pools.md b/developer/system/storage-pools.md index 2f00b380..7f0970aa 100644 --- a/developer/system/storage-pools.md +++ b/developer/system/storage-pools.md @@ -6,7 +6,6 @@ ref: 57 title: Storage Pools --- - Qubes OS R3.2 introduced the concept of storage drivers and pools. This feature was a first step towards a saner storage API, which is heavily rewritten in R4. See [here](https://dev.qubes-os.org/projects/core-admin/en/latest/qubes-storage.html) diff --git a/developer/system/template-implementation.md b/developer/system/template-implementation.md index cdf525bf..de754f95 100644 --- a/developer/system/template-implementation.md +++ b/developer/system/template-implementation.md @@ -10,7 +10,6 @@ ref: 58 title: Template Implementation --- - Every VM has 4 block devices connected: - **xvda** – base root device (/) – details described below diff --git a/introduction/code-of-conduct.md b/introduction/code-of-conduct.md index 571794ef..b585c996 100644 --- a/introduction/code-of-conduct.md +++ b/introduction/code-of-conduct.md @@ -114,4 +114,3 @@ The initial published version of this Code of Conduct was adapted from the [Contributor Covenant, version 1.4](https://contributor-covenant.org/version/1/4) and the [Rust Code of Conduct](https://www.rust-lang.org/en-US/conduct.html). - diff --git a/introduction/contributing.md b/introduction/contributing.md index e2b3ff00..e6eba1d9 100644 --- a/introduction/contributing.md +++ b/introduction/contributing.md @@ -58,4 +58,3 @@ time, like implementing a new feature, it's always good to contact us first, preferably via the [qubes-devel](/support/#qubes-devel) mailing list. Once we've worked out the details, we'll be grateful to [receive your patch](/doc/source-code/#how-to-send-patches). - diff --git a/introduction/faq.md b/introduction/faq.md index fdcffef4..7c2c57f6 100644 --- a/introduction/faq.md +++ b/introduction/faq.md @@ -694,4 +694,3 @@ If you need to support not-fully-updated systems, check for the existence of `/u Yes, Qubes natively supports automation via [Salt (SaltStack)](/doc/salt/). There is also the unofficial [ansible-qubes toolkit](https://github.com/Rudd-O/ansible-qubes). (**Warning:** Since this is an external project that has not been reviewed or endorsed by the Qubes team, [allowing it to manage dom0 may be a security risk](https://github.com/Qubes-Community/Contents/blob/master/docs/security/security-guidelines.md#dom0-precautions).) - diff --git a/introduction/screenshots.md b/introduction/screenshots.md index 5d2d6fbd..1f4b04d0 100644 --- a/introduction/screenshots.md +++ b/introduction/screenshots.md @@ -10,7 +10,6 @@ ref: 123 title: Screenshots --- - [![r4.0-xfce-desktop.png](/attachment/doc/r4.0-xfce-desktop.png)](/attachment/doc/r4.0-xfce-desktop.png) The default desktop environment is Xfce4. diff --git a/introduction/statistics.md b/introduction/statistics.md index 3f961ac9..851a0e12 100644 --- a/introduction/statistics.md +++ b/introduction/statistics.md @@ -59,4 +59,3 @@ The raw data is available [here](https://tools.qubes-os.org/counter/stats.json). (This does not include any personally-identifying user data.) Please note that the format of this data is not documented and may change any time if the developers feel the need to include something else. The source code is available [here](https://github.com/woju/qubes-stats). - diff --git a/project-security/security-pack.md b/project-security/security-pack.md index c4938f34..ea5d513a 100644 --- a/project-security/security-pack.md +++ b/project-security/security-pack.md @@ -270,4 +270,3 @@ Qubes binaries :/ implement multiple signature scheme for distributed binaries. ``` - diff --git a/project-security/security.md b/project-security/security.md index 14c3d313..738236e2 100644 --- a/project-security/security.md +++ b/project-security/security.md @@ -87,4 +87,3 @@ about how to authenticate these keys. - [Marek Marczykowski-Górecki](/team/#marek-marczykowski-górecki) - [Simon Gaiser (aka HW42)](/team/#simon-gaiser-aka-hw42) - [Joanna Rutkowska](/team/#joanna-rutkowska) ([emeritus, canaries only](/news/2018/11/05/qubes-security-team-update/)) - diff --git a/project-security/verifying-signatures.md b/project-security/verifying-signatures.md index 8de6db83..cae3b045 100644 --- a/project-security/verifying-signatures.md +++ b/project-security/verifying-signatures.md @@ -664,4 +664,3 @@ If your question is about GPG, please see the [GPG documentation](https://www.gnupg.org/documentation/). Still have question? Please see [Help, Support, Mailing Lists, and Forum](/support/) for places where you can ask! - diff --git a/project-security/xsa.md b/project-security/xsa.md index 3cb9f1f6..b14ae38b 100644 --- a/project-security/xsa.md +++ b/project-security/xsa.md @@ -40,4 +40,3 @@ or **No**. completeness, but they are excluded from the [Statistics](#statistics) section for the sake of accuracy. * All dates are in UTC. - diff --git a/user/advanced-topics/awesomewm.md b/user/advanced-topics/awesomewm.md index 88659d84..28f969da 100644 --- a/user/advanced-topics/awesomewm.md +++ b/user/advanced-topics/awesomewm.md @@ -9,7 +9,6 @@ ref: 179 title: AwesomeWM (window manager) --- - ## Qubes-specific features * support for the Qubes OS window colors diff --git a/user/advanced-topics/bind-dirs.md b/user/advanced-topics/bind-dirs.md index 2eaedc3d..67ca82b0 100644 --- a/user/advanced-topics/bind-dirs.md +++ b/user/advanced-topics/bind-dirs.md @@ -8,7 +8,6 @@ ref: 186 title: How to Make Any File Persistent (bind-dirs) --- - ## What are bind-dirs? ## With [bind-dirs](https://github.com/QubesOS/qubes-core-agent-linux/blob/master/vm-systemd/bind-dirs.sh) @@ -103,4 +102,3 @@ binds=( "${binds[@]/'/var/lib/tor'}" ) ## Discussion ## [app qubes: make selected files and folders located in the root image persistent- review bind-dirs.sh](https://groups.google.com/forum/#!topic/qubes-devel/tcYQ4eV-XX4/discussion) - diff --git a/user/advanced-topics/config-files.md b/user/advanced-topics/config-files.md index bc55048a..7ab46faa 100644 --- a/user/advanced-topics/config-files.md +++ b/user/advanced-topics/config-files.md @@ -11,7 +11,6 @@ ref: 180 title: Config Files --- - Qubes-specific VM config files ------------------------------ diff --git a/user/advanced-topics/disposable-customization.md b/user/advanced-topics/disposable-customization.md index 04621774..2368ef67 100644 --- a/user/advanced-topics/disposable-customization.md +++ b/user/advanced-topics/disposable-customization.md @@ -13,7 +13,6 @@ ref: 174 title: Disposable Customization --- - ## Introduction A [disposable](/doc/disposable/) can be based on any [app qube](/doc/glossary/#app-qube). diff --git a/user/advanced-topics/gui-configuration.md b/user/advanced-topics/gui-configuration.md index 1c145b08..a4420a01 100644 --- a/user/advanced-topics/gui-configuration.md +++ b/user/advanced-topics/gui-configuration.md @@ -6,7 +6,6 @@ ref: 184 title: GUI Configuration --- - ## Video RAM adjustment for high-resolution displays When a qube starts, a fixed amount of RAM is allocated to the graphics buffer called video RAM. diff --git a/user/advanced-topics/how-to-install-software-in-dom0.md b/user/advanced-topics/how-to-install-software-in-dom0.md index 398eab28..163fd451 100644 --- a/user/advanced-topics/how-to-install-software-in-dom0.md +++ b/user/advanced-topics/how-to-install-software-in-dom0.md @@ -246,4 +246,3 @@ sys-whonix. ``` Qubes VM Manager -> System -> Global Settings -> UpdateVM -> sys-whonix ``` - diff --git a/user/advanced-topics/i3.md b/user/advanced-topics/i3.md index 43cfed2b..b326988d 100644 --- a/user/advanced-topics/i3.md +++ b/user/advanced-topics/i3.md @@ -10,7 +10,6 @@ ref: 183 title: i3 (window manager) --- - i3 is part of the stable repository (as of Qubes R3.1) and can be installed by using the [dom0 update mechanism](/doc/how-to-install-software-in-dom0/). To install the i3 window manager and the its Qubes specific configuration: diff --git a/user/advanced-topics/installing-contributed-packages.md b/user/advanced-topics/installing-contributed-packages.md index dc4724d1..8bc2e347 100644 --- a/user/advanced-topics/installing-contributed-packages.md +++ b/user/advanced-topics/installing-contributed-packages.md @@ -6,7 +6,6 @@ ref: 225 title: Installing Contributed Packages --- - _This page is for users who wish to install contributed packages. If you want to contribute a package, please see [package contributions](/doc/package-contributions/)._ @@ -55,4 +54,3 @@ sudo qubes-dom0-update --clean qvm-screenshot-tool ``` Please see the package's README for specific installation and setup instructions. - diff --git a/user/advanced-topics/kde.md b/user/advanced-topics/kde.md index 166400e1..5d350b06 100644 --- a/user/advanced-topics/kde.md +++ b/user/advanced-topics/kde.md @@ -8,7 +8,6 @@ ref: 176 title: KDE (desktop environment) --- - Installation ------------ diff --git a/user/advanced-topics/managing-vm-kernels.md b/user/advanced-topics/managing-vm-kernels.md index 4fd3574b..6460658a 100644 --- a/user/advanced-topics/managing-vm-kernels.md +++ b/user/advanced-topics/managing-vm-kernels.md @@ -9,7 +9,6 @@ ref: 173 title: Managing VM Kernels --- - By default, VMs kernels are provided by dom0. (See [here](/doc/how-to-install-software-in-dom0/#kernel-upgrade) for information about upgrading kernels in dom0.) This means that: @@ -362,4 +361,3 @@ update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64 #### Troubleshooting In case of problems, visit the [VM Troubleshooting guide](/doc/vm-troubleshooting/#vm-kernel-troubleshooting) to learn how to access the VM console, view logs and fix a VM kernel installation. - diff --git a/user/advanced-topics/mount-from-other-os.md b/user/advanced-topics/mount-from-other-os.md index bb907aab..ec0427dc 100644 --- a/user/advanced-topics/mount-from-other-os.md +++ b/user/advanced-topics/mount-from-other-os.md @@ -10,7 +10,6 @@ ref: 175 title: How to Mount a Qubes Partition from Another OS --- - When a Qubes OS install is unbootable or booting it is otherwise undesirable, this process allows for the recovery of files stored within the system. These functions are manual and do not require any Qubes specific tools. All steps assume the default Qubes install with the following components: diff --git a/user/advanced-topics/resize-disk-image.md b/user/advanced-topics/resize-disk-image.md index 290cba01..98ffa74a 100644 --- a/user/advanced-topics/resize-disk-image.md +++ b/user/advanced-topics/resize-disk-image.md @@ -107,4 +107,3 @@ sudo lvresize --size 1024M /dev/qubes_dom0/vm-qube1-private ``` If you have a SSD see [here](/doc/disk-trim) for information on using fstrim. - diff --git a/user/advanced-topics/rpc-policy.md b/user/advanced-topics/rpc-policy.md index 75d738af..19dd9f73 100644 --- a/user/advanced-topics/rpc-policy.md +++ b/user/advanced-topics/rpc-policy.md @@ -6,7 +6,6 @@ ref: 178 title: RPC Policies --- - This document explains the basics of RPC policies in Qubes. For more information, see [Qrexec: command execution in VMs](/doc/qrexec3/). @@ -67,4 +66,3 @@ Further details about how this system works can be found in [Qrexec: command exe (***Note**: the `$` character is deprecated in qrexec keywords -- please use `@` instead (e.g. `@anyvm`). For more information, see the bulletin [here](https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-038-2018.txt).*) - diff --git a/user/advanced-topics/salt.md b/user/advanced-topics/salt.md index 1a32083c..e565c19e 100644 --- a/user/advanced-topics/salt.md +++ b/user/advanced-topics/salt.md @@ -608,4 +608,3 @@ install template and shutdown updateVM: - [Jinja templates](http://jinja.pocoo.org/) - [Qubes specific modules](https://github.com/QubesOS/qubes-mgmt-salt-dom0-qvm/blob/master/README.rst) - [Formulas for default Qubes VMs](https://github.com/QubesOS/qubes-mgmt-salt-dom0-virtual-machines/tree/master/qvm) - diff --git a/user/advanced-topics/secondary-storage.md b/user/advanced-topics/secondary-storage.md index ede40e7b..be01f454 100644 --- a/user/advanced-topics/secondary-storage.md +++ b/user/advanced-topics/secondary-storage.md @@ -10,7 +10,6 @@ ref: 187 title: Secondary Storage --- - Suppose you have a fast but small primary SSD and a large but slow secondary HDD. You want to store a subset of your app qubes on the HDD. @@ -112,4 +111,3 @@ By default VMs will be created on the main Qubes disk (i.e. a small SSD), to cre ``` qvm-create -P poolhd0_qubes --label red unstrusted-hdd ``` - diff --git a/user/advanced-topics/usb-qubes.md b/user/advanced-topics/usb-qubes.md index 1e20bd82..bc978633 100644 --- a/user/advanced-topics/usb-qubes.md +++ b/user/advanced-topics/usb-qubes.md @@ -12,7 +12,6 @@ ref: 181 title: USB Qubes --- - If during installation you enabled the creation of a USB-qube, your system should be setup already and none of the mentioned steps here should be necessary. (Unless you want to [remove your USB-qube](#removing-a-usb-qube).) If for any reason no USB-qube was created during installation, this guide will show you how to do so. **Caution:** If you want to use a USB-keyboard, please beware of the possibility to lock yourself out! To avoid this problem [enable your keyboard for login](#enable-a-usb-keyboard-for-login)! @@ -201,4 +200,3 @@ The procedure to hide all USB controllers from dom0 is as follows: 5. If `rd.qubes.hide_all_usb` appears anywhere in those lines, remove it. 6. Save and close the file. 7. Reboot. - diff --git a/user/advanced-topics/volume-backup-revert.md b/user/advanced-topics/volume-backup-revert.md index ccdda313..417c93f6 100644 --- a/user/advanced-topics/volume-backup-revert.md +++ b/user/advanced-topics/volume-backup-revert.md @@ -10,7 +10,6 @@ ref: 206 title: Volume Backup and Revert --- - With Qubes, it is possible to revert one of a VM's storage volumes to a previous state using the automatic snapshot that is normally saved every time a VM is shutdown. (Note that this is a different, lower level activity than the diff --git a/user/advanced-topics/windows.md b/user/advanced-topics/windows.md index bd2c3720..347f17b6 100644 --- a/user/advanced-topics/windows.md +++ b/user/advanced-topics/windows.md @@ -6,7 +6,6 @@ ref: 129 title: Windows VMs --- - Like any other unmodified OSes, Windows can be installed in Qubes as an [HVM](/doc/standalone-and-hvm/) domain. Qubes Windows Tools are then usually installed to provide integration with the rest of the Qubes system; they also include Xen's paravirtualized (PV) drivers to increase performance compared to qemu emulated devices. Alternatively, only Xen's PV drivers can be installed if integration with Qubes isn't required or if the tools aren't supported on a give version of Windows. In the latter case, one would have to [enable inter-VM networking](/doc/firewall/#enabling-networking-between-two-qubes) to be able to exchange files with HVMs. diff --git a/user/downloading-installing-upgrading/custom-install.md b/user/downloading-installing-upgrading/custom-install.md index cd3e2b1e..4b774f39 100644 --- a/user/downloading-installing-upgrading/custom-install.md +++ b/user/downloading-installing-upgrading/custom-install.md @@ -9,7 +9,6 @@ advanced: true title: Custom Installation --- - In the present context, "custom installation" refers to things like manual partitioning, setting up LVM and RAID, and manual LUKS encryption configuration. ## Installer Defaults @@ -161,4 +160,3 @@ Boot into the Qubes installer, then press `ctrl`+`alt`+`F2` to get a virtual con Repeat the process for `sda1` and `qubes_dom0-swap`. Those should be assigned to `/boot` and `swap` respectively. The default file systems are ext4 for `/boot` and `/`, and swap for `swap`. When you are finished, the Unknown list should go away, and all three mount points should be assigned. Proceed normally with the installation from there. - diff --git a/user/downloading-installing-upgrading/download-mirrors.md b/user/downloading-installing-upgrading/download-mirrors.md index ff26f09d..4220ea00 100644 --- a/user/downloading-installing-upgrading/download-mirrors.md +++ b/user/downloading-installing-upgrading/download-mirrors.md @@ -25,4 +25,3 @@ helpful in streamlining the process. every 6-8 hours is fine. * For technical accommodations, please contact [Wojtek](/team/#wojtek-porczyk) or [Marek](/team/#marek-marczykowski-górecki). * For website updates and fixes, please contact [Andrew](/team/#andrew-david-wong). - diff --git a/user/downloading-installing-upgrading/install-security.md b/user/downloading-installing-upgrading/install-security.md index c1aee91e..4ee21ff4 100644 --- a/user/downloading-installing-upgrading/install-security.md +++ b/user/downloading-installing-upgrading/install-security.md @@ -10,7 +10,6 @@ ref: 149 title: Installation security --- - There are several security matters to consider before and during the Qubes installation process. ## Trusting your hardware @@ -77,4 +76,3 @@ Cons: (Option 3 violates the Qubes security model since it entails transferring an untrusted ISO to dom0 in order to burn it to disc, which leaves only the other two options.) Considering the pros and cons of each, perhaps a USB drive with non-rewritable (or at least cryptographically-signed) firmware and a physical write-protect switch might be the best option. - diff --git a/user/downloading-installing-upgrading/installation-guide.md b/user/downloading-installing-upgrading/installation-guide.md index 0a4a5876..284ae15d 100644 --- a/user/downloading-installing-upgrading/installation-guide.md +++ b/user/downloading-installing-upgrading/installation-guide.md @@ -472,4 +472,3 @@ the other [How-to Guides](/doc/#how-to-guides), and learn about * Please do **not** email individual members of the Qubes team with questions about installation or other problems. Instead, please see [Help, Support, Mailing Lists, and Forum](/support/) for appropriate places to ask questions. - diff --git a/user/downloading-installing-upgrading/supported-versions.md b/user/downloading-installing-upgrading/supported-versions.md index bda4e0cf..68da7909 100644 --- a/user/downloading-installing-upgrading/supported-versions.md +++ b/user/downloading-installing-upgrading/supported-versions.md @@ -129,4 +129,3 @@ templates within a month of their respective releases. To be precise: We aim to announce both types of events one month in advance in order to remind users to upgrade. - diff --git a/user/downloading-installing-upgrading/upgrade/upgrade-to-r2.md b/user/downloading-installing-upgrading/upgrade/upgrade-to-r2.md index d743e72c..681bd784 100644 --- a/user/downloading-installing-upgrading/upgrade/upgrade-to-r2.md +++ b/user/downloading-installing-upgrading/upgrade/upgrade-to-r2.md @@ -11,7 +11,6 @@ ref: 156 title: Upgrading to R2 --- - Current Qubes R2 Beta 3 (R2B3) systems can be upgraded in-place to the latest R2 (R2) release by following the procedure below. **Before attempting either an in-place upgrade or a clean installation, we strongly recommend that users back up the system by using the built-in [backup tool](/doc/backup-restore/).** diff --git a/user/downloading-installing-upgrading/upgrade/upgrade-to-r2b1.md b/user/downloading-installing-upgrading/upgrade/upgrade-to-r2b1.md index d7beef28..5d22eb64 100644 --- a/user/downloading-installing-upgrading/upgrade/upgrade-to-r2b1.md +++ b/user/downloading-installing-upgrading/upgrade/upgrade-to-r2b1.md @@ -10,7 +10,6 @@ ref: 163 title: Upgrading to R2B1 --- - **Note: Qubes R2 Beta 1 is no longer supported! Please install or upgrade to a newer Qubes R2.** **Note: This page is kept for historical reasons only! Do not follow the instructions below'''** diff --git a/user/downloading-installing-upgrading/upgrade/upgrade-to-r2b2.md b/user/downloading-installing-upgrading/upgrade/upgrade-to-r2b2.md index 5d209b9a..88bfc86b 100644 --- a/user/downloading-installing-upgrading/upgrade/upgrade-to-r2b2.md +++ b/user/downloading-installing-upgrading/upgrade/upgrade-to-r2b2.md @@ -10,7 +10,6 @@ ref: 160 title: Upgrading to R2B2 --- - Existing users of Qubes R1 (but not R1 betas!) can upgrade their systems to the latest R2 beta release by following the procedure below. As usual, it is advisable to backup the system before proceeding with the upgrade. While it is possible to upgrade the system **it is strongly recommended to reinstall it**. You will preserve all your data and settings thanks to [backup and restore tools](/doc/backup-restore/). Upgrade all Template and Standalone VM(s) diff --git a/user/downloading-installing-upgrading/upgrade/upgrade-to-r2b3.md b/user/downloading-installing-upgrading/upgrade/upgrade-to-r2b3.md index 305fe047..18916dee 100644 --- a/user/downloading-installing-upgrading/upgrade/upgrade-to-r2b3.md +++ b/user/downloading-installing-upgrading/upgrade/upgrade-to-r2b3.md @@ -10,7 +10,6 @@ ref: 157 title: Upgrading to R2B3 --- - Current Qubes R2 Beta 2 (R2B2) systems can be upgraded in-place to the latest R2 Beta 3 (R2B3) release by following the procedure below. However, upgrading in-place is riskier than performing a clean installation, since there are more things which can go wrong. For this reason, **we strongly recommended that users perform a [clean installation](/doc/installation-guide/) of Qubes R2 Beta 3**. **Before attempting either an in-place upgrade or a clean installation, we strongly recommend that users back up the system by using the built-in [backup tool](/doc/backup-restore/).** diff --git a/user/downloading-installing-upgrading/upgrade/upgrade-to-r3_0.md b/user/downloading-installing-upgrading/upgrade/upgrade-to-r3_0.md index 16cd169e..19082f64 100644 --- a/user/downloading-installing-upgrading/upgrade/upgrade-to-r3_0.md +++ b/user/downloading-installing-upgrading/upgrade/upgrade-to-r3_0.md @@ -10,7 +10,6 @@ ref: 159 title: Upgrading to R3.0 --- - **This instruction is highly experimental, the official way to upgrade from R2 is to backup the data and reinstall the system. Use at your own risk!** Current Qubes R3.0 (R3.0) systems can be upgraded in-place to the latest R3.0 by following the procedure below. However, upgrading in-place is riskier than performing a clean installation, since there are more things which can go wrong. For this reason, **we strongly recommended that users perform a [clean installation](/doc/installation-guide/) of Qubes R3.0**. diff --git a/user/downloading-installing-upgrading/upgrade/upgrade-to-r3_1.md b/user/downloading-installing-upgrading/upgrade/upgrade-to-r3_1.md index 35e603bc..527434ca 100644 --- a/user/downloading-installing-upgrading/upgrade/upgrade-to-r3_1.md +++ b/user/downloading-installing-upgrading/upgrade/upgrade-to-r3_1.md @@ -10,7 +10,6 @@ ref: 155 title: Upgrading to R3.1 --- - **Before attempting either an in-place upgrade or a clean installation, we strongly recommend that users [back up their systems](/doc/backup-restore/).** diff --git a/user/downloading-installing-upgrading/upgrade/upgrade-to-r3_2.md b/user/downloading-installing-upgrading/upgrade/upgrade-to-r3_2.md index 5140c7f2..1f26854c 100644 --- a/user/downloading-installing-upgrading/upgrade/upgrade-to-r3_2.md +++ b/user/downloading-installing-upgrading/upgrade/upgrade-to-r3_2.md @@ -10,7 +10,6 @@ ref: 161 title: Upgrading to R3.2 --- - **Before attempting either an in-place upgrade or a clean installation, we strongly recommend that users [back up their systems](/doc/backup-restore/).** diff --git a/user/downloading-installing-upgrading/upgrade/upgrade-to-r4_0.md b/user/downloading-installing-upgrading/upgrade/upgrade-to-r4_0.md index c002fb13..5b66a8eb 100644 --- a/user/downloading-installing-upgrading/upgrade/upgrade-to-r4_0.md +++ b/user/downloading-installing-upgrading/upgrade/upgrade-to-r4_0.md @@ -10,7 +10,6 @@ ref: 162 title: Upgrading to R4.0 --- - **Before attempting either an in-place upgrade or a clean installation, we strongly recommend that users [back up their systems](/doc/backup-restore/).** Current Qubes R3.2 systems cannot be upgraded in-place to R4.0. @@ -116,4 +115,3 @@ Please see [Supported Versions](/doc/supported-versions/) for information on sup * [Upgrading Fedora templates](/doc/templates/fedora/#upgrading) * [Upgrading Debian templates](/doc/templates/debian/#upgrading) * [Updating Whonix templates](https://www.whonix.org/wiki/Qubes/Update) - diff --git a/user/downloading-installing-upgrading/upgrade/upgrade.md b/user/downloading-installing-upgrading/upgrade/upgrade.md index 0fe171d4..cab6117c 100644 --- a/user/downloading-installing-upgrading/upgrade/upgrade.md +++ b/user/downloading-installing-upgrading/upgrade/upgrade.md @@ -6,7 +6,6 @@ ref: 158 title: Upgrade Guides --- - These guides are for upgrading from one version of Qubes to another. If you're just looking to update your system while staying on the same version, see [How to Update](/doc/how-to-update/). @@ -19,4 +18,3 @@ see [How to Update](/doc/how-to-update/). * [Upgrading from R3.0 to R3.1](/doc/upgrade-to-r3.1/) * [Upgrading from R3.1 to R3.2](/doc/upgrade-to-r3.2/) * [Upgrading from R3.2 to R4.0](/doc/upgrade-to-r4.0/) - diff --git a/user/hardware/certified-hardware.md b/user/hardware/certified-hardware.md index 113b99f2..94beb66f 100644 --- a/user/hardware/certified-hardware.md +++ b/user/hardware/certified-hardware.md @@ -10,7 +10,6 @@ ref: 144 title: Certified Hardware --- - The Qubes OS Project aims to partner with a select few computer vendors to ensure that Qubes users have reliable hardware purchasing options. We aim for these vendors to be as diverse as possible in terms of geography, cost, and availability. @@ -105,4 +104,3 @@ This could be done by consulting the [Hardware Compatibility List](/hcl/) or try While we are willing to troubleshoot simple issues, we will need to charge a consulting fee for more in-depth work. If you are interested in having your hardware certified, please [contact us](mailto:business@qubes-os.org). - diff --git a/user/hardware/hardware-testing.md b/user/hardware/hardware-testing.md index dcf65ce1..170df9ef 100644 --- a/user/hardware/hardware-testing.md +++ b/user/hardware/hardware-testing.md @@ -6,7 +6,6 @@ ref: 145 title: Hardware Testing --- - The Qubes developers test Qubes OS on certain hardware models. The tested hardware described on this page differs from [Qubes Certified Hardware](/doc/certified-hardware/) in a few key ways: @@ -38,4 +37,3 @@ If anyone is willing to lend or donate these models to us, we would be happy to - Dell Latitude with Intel 8th Gen CPU and integrated graphics Note: The Lenovo X and T series are similar enough to assume similar compatibility of the matching model from the other series. - diff --git a/user/hardware/hcl.md b/user/hardware/hcl.md index cd7017f9..c5d7952a 100644 --- a/user/hardware/hcl.md +++ b/user/hardware/hcl.md @@ -12,7 +12,6 @@ ref: 146 title: Hardware Compatibility List (HCL) --- - The [HCL](/hcl) is a compilation of reports generated and submitted by users across various Qubes versions about their hardware's compatibility with Qubes. **Note:** @@ -46,4 +45,3 @@ Please consider sending the **HCL Support Files** `.cpio.gz` file as well. To ge **Please note:** The **HCL Support Files** may contain numerous hardware details, including serial numbers. If, for privacy or security reasons, you do not wish to make this information public, please **do not** send the `.cpio.gz` file to the public mailing list. - diff --git a/user/hardware/system-requirements.md b/user/hardware/system-requirements.md index 838090d5..a7cb0df5 100644 --- a/user/hardware/system-requirements.md +++ b/user/hardware/system-requirements.md @@ -84,4 +84,3 @@ title: System Requirements notebook](https://groups.google.com/d/msg/qubes-users/Sz0Nuhi4N0o/ZtpJdoc0OY8J). - You can check whether an Intel processor has VT-x and VT-d on [ark.intel.com](https://ark.intel.com/content/www/us/en/ark.html#@Processors). - diff --git a/user/how-to-guides/backup-emergency-restore-v2.md b/user/how-to-guides/backup-emergency-restore-v2.md index 73731383..9cc0c23c 100644 --- a/user/how-to-guides/backup-emergency-restore-v2.md +++ b/user/how-to-guides/backup-emergency-restore-v2.md @@ -9,7 +9,6 @@ ref: 207 title: Emergency Backup Recovery (v2) --- - This page describes how to perform emergency restore of backup created on Qubes R2 Beta3 or earlier (which uses backup format 2). diff --git a/user/how-to-guides/backup-emergency-restore-v3.md b/user/how-to-guides/backup-emergency-restore-v3.md index fa0a716c..1abab60e 100644 --- a/user/how-to-guides/backup-emergency-restore-v3.md +++ b/user/how-to-guides/backup-emergency-restore-v3.md @@ -9,7 +9,6 @@ ref: 201 title: Emergency Backup Recovery (v3) --- - This page describes how to perform an emergency restore of a backup created on Qubes R2 or later (which uses backup format version 3). diff --git a/user/how-to-guides/backup-emergency-restore-v4.md b/user/how-to-guides/backup-emergency-restore-v4.md index ca8c745e..9a7ec00c 100644 --- a/user/how-to-guides/backup-emergency-restore-v4.md +++ b/user/how-to-guides/backup-emergency-restore-v4.md @@ -9,7 +9,6 @@ ref: 192 title: Emergency Backup Recovery (v4) --- - This page describes how to perform an emergency restore of a backup created on Qubes R4.X (which uses backup format version 4). @@ -179,4 +178,3 @@ Emergency Recovery Instructions repository: https://github.com/QubesOS/qubes-doc.git - diff --git a/user/how-to-guides/how-to-copy-and-move-files.md b/user/how-to-guides/how-to-copy-and-move-files.md index c66f622b..987f12d3 100644 --- a/user/how-to-guides/how-to-copy-and-move-files.md +++ b/user/how-to-guides/how-to-copy-and-move-files.md @@ -11,7 +11,6 @@ ref: 191 title: How to Copy and Move Files --- - *This page is about copying and moving files. If you wish to simply copy and paste text, that can be done more easily using the inter-qube clipboard. See [copying and pasting text between qubes](/doc/how-to-copy-and-paste-text/). diff --git a/user/how-to-guides/how-to-copy-and-paste-text.md b/user/how-to-guides/how-to-copy-and-paste-text.md index f8fb9c48..791acc6e 100644 --- a/user/how-to-guides/how-to-copy-and-paste-text.md +++ b/user/how-to-guides/how-to-copy-and-paste-text.md @@ -11,7 +11,6 @@ ref: 196 title: How to Copy and Paste Text --- - *This page is about copying and pasting plain text. If you wish to copy more complex data, such as rich text or images, see [copying and moving files between qubes](/doc/how-to-copy-and-move-files/). For dom0, see [copying from (and to) dom0](/doc/how-to-copy-from-dom0/).* 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 e2cf3c75..a7d10ee5 100644 --- a/user/how-to-guides/how-to-copy-from-dom0.md +++ b/user/how-to-guides/how-to-copy-from-dom0.md @@ -12,7 +12,6 @@ ref: 198 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/). 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 84d832d9..e5844538 100644 --- a/user/how-to-guides/how-to-enter-fullscreen-mode.md +++ b/user/how-to-guides/how-to-enter-fullscreen-mode.md @@ -11,7 +11,6 @@ ref: 205 title: How to Enter Fullscreen Mode --- - What is fullscreen mode? ------------------------- diff --git a/user/how-to-guides/how-to-use-block-storage-devices.md b/user/how-to-guides/how-to-use-block-storage-devices.md index c408ba70..9ca24628 100644 --- a/user/how-to-guides/how-to-use-block-storage-devices.md +++ b/user/how-to-guides/how-to-use-block-storage-devices.md @@ -12,7 +12,6 @@ ref: 193 title: How to Use Block Storage Devices --- - *This page is part of [device handling in qubes](/doc/how-to-use-devices/).* If you don't know what a "block device" is, just think of it as a fancy way to say "something that stores data". @@ -255,4 +254,3 @@ qvm-block a work sys-usb:sda1 -o devtype=cdrom ``` This option accepts `cdrom` and `disk`, default is `disk`. - diff --git a/user/how-to-guides/how-to-use-devices.md b/user/how-to-guides/how-to-use-devices.md index fb767986..b3c3f0a5 100644 --- a/user/how-to-guides/how-to-use-devices.md +++ b/user/how-to-guides/how-to-use-devices.md @@ -12,7 +12,6 @@ ref: 188 title: How to Use Devices --- - This is an overview of device handling in Qubes OS. For specific devices ([block](/doc/how-to-use-block-storage-devices/), [USB](/doc/how-to-use-usb-devices/) and [PCI](/doc/how-to-use-pci-devices/) devices), please visit their respective pages. @@ -157,4 +156,3 @@ If no specific `sourceVM:deviceID` combination is given, *all devices of that DE **SYNOPSIS** `qvm-device DEVICE_CLASS {detach|dt|d} targetVM [sourceVM:deviceID]` - diff --git a/user/how-to-guides/how-to-use-disposables.md b/user/how-to-guides/how-to-use-disposables.md index 6ffb1788..3ca8507b 100644 --- a/user/how-to-guides/how-to-use-disposables.md +++ b/user/how-to-guides/how-to-use-disposables.md @@ -188,4 +188,3 @@ More information about RPC policies for disposables can be found [here](/doc/qre You can change the template used to generate the disposables, and change settings used in the disposable savefile. These changes will be reflected in every new disposable based on that template. Full instructions can be found [here](/doc/disposable-customization/). - diff --git a/user/how-to-guides/how-to-use-optical-discs.md b/user/how-to-guides/how-to-use-optical-discs.md index 84ecb060..d4287ead 100644 --- a/user/how-to-guides/how-to-use-optical-discs.md +++ b/user/how-to-guides/how-to-use-optical-discs.md @@ -10,7 +10,6 @@ ref: 204 title: How to Use Optical Discs --- - Passthrough reading and recording (a.k.a., "burning") are not supported by Xen. Currently, the only options for reading and recording optical discs (e.g., CDs, DVDs, BRDs) in Qubes are: diff --git a/user/how-to-guides/how-to-use-pci-devices.md b/user/how-to-guides/how-to-use-pci-devices.md index 4473cd49..820825c9 100644 --- a/user/how-to-guides/how-to-use-pci-devices.md +++ b/user/how-to-guides/how-to-use-pci-devices.md @@ -12,7 +12,6 @@ ref: 197 title: How to Use PCI Devices --- - *This page is part of [device handling in qubes](/doc/how-to-use-devices/).* **Warning:** Only dom0 exposes PCI devices. @@ -142,4 +141,3 @@ or ``` It is **strongly discouraged to reattach PCI devices to dom0**, especially if they don't support resetting! - diff --git a/user/how-to-guides/how-to-use-usb-devices.md b/user/how-to-guides/how-to-use-usb-devices.md index 407f696f..9261a4ee 100644 --- a/user/how-to-guides/how-to-use-usb-devices.md +++ b/user/how-to-guides/how-to-use-usb-devices.md @@ -9,7 +9,6 @@ ref: 195 title: How to Use USB Devices --- - *This page is part of [device handling in qubes](/doc/how-to-use-devices/).* If you are looking to handle USB *storage* devices (thumbdrives or USB-drives), please have a look at the [block device](/doc/how-to-use-block-storage-devices/) page. @@ -155,4 +154,3 @@ Now you see the path and the text between `/pci0000:00/0000:` and `/usb3` i.e. ` For example, On R 4.0 the command would look something like `qvm-pci attach --persistent personal dom0:00_1a.0` - diff --git a/user/reference/glossary.md b/user/reference/glossary.md index 1d2f11e1..b5593587 100644 --- a/user/reference/glossary.md +++ b/user/reference/glossary.md @@ -213,4 +213,3 @@ See [Templates](/doc/templates/). An abbreviation for "virtual machine." A software implementation of a machine (for example, a computer) that executes programs like a physical machine. - diff --git a/user/reference/tools.md b/user/reference/tools.md index 4f1a2bed..0494ae38 100644 --- a/user/reference/tools.md +++ b/user/reference/tools.md @@ -13,7 +13,6 @@ ref: 141 title: Command-line Tools --- - Dom0 ---- diff --git a/user/security-in-qubes/anti-evil-maid.md b/user/security-in-qubes/anti-evil-maid.md index 93d49e06..89482d47 100644 --- a/user/security-in-qubes/anti-evil-maid.md +++ b/user/security-in-qubes/anti-evil-maid.md @@ -10,7 +10,6 @@ ref: 164 title: Anti Evil Maid (AEM) --- - Background ---------- diff --git a/user/security-in-qubes/data-leaks.md b/user/security-in-qubes/data-leaks.md index 99b32f16..ec357ebe 100644 --- a/user/security-in-qubes/data-leaks.md +++ b/user/security-in-qubes/data-leaks.md @@ -10,7 +10,6 @@ ref: 171 title: Data Leaks --- - The Role of the Firewall ------------------------ diff --git a/user/security-in-qubes/device-handling-security.md b/user/security-in-qubes/device-handling-security.md index 1208a180..a67a7b64 100644 --- a/user/security-in-qubes/device-handling-security.md +++ b/user/security-in-qubes/device-handling-security.md @@ -6,7 +6,6 @@ ref: 170 title: Device Handling Security --- - Any additional ability a VM gains is additional attack surface. It's a good idea to always attach the minimum entity required in a VM. @@ -73,4 +72,3 @@ One possibility is to set up the screen locker to require an additional step to One way to achieve this is to use a [YubiKey](/doc/YubiKey/), or some other hardware token, or even to manually enter a one-time password. Support for [two factor authentication](/news/2018/09/11/qubes-u2f-proxy/) was recently added, though there are [issues](https://github.com/QubesOS/qubes-issues/issues/4661). - diff --git a/user/security-in-qubes/split-gpg.md b/user/security-in-qubes/split-gpg.md index e70c7ef1..bab2c917 100644 --- a/user/security-in-qubes/split-gpg.md +++ b/user/security-in-qubes/split-gpg.md @@ -398,4 +398,3 @@ As always, exercise caution and use your good judgment.) Note that `pinentry` might show an error when you try to set an empty passphrase, but it will still make the change. (See [this StackExchange answer](https://unix.stackexchange.com/a/379373) for more information.) Note: The error shows only if you **do not** have graphical pinentry installed. - diff --git a/user/security-in-qubes/u2f-proxy.md b/user/security-in-qubes/u2f-proxy.md index 0d13a0e9..b1836f3c 100644 --- a/user/security-in-qubes/u2f-proxy.md +++ b/user/security-in-qubes/u2f-proxy.md @@ -6,7 +6,6 @@ ref: 167 title: U2F Proxy --- - The [Qubes U2F Proxy](https://github.com/QubesOS/qubes-app-u2f) is a secure proxy intended to make use of U2F two-factor authentication devices with web browsers without exposing the browser to the full USB stack, not unlike the [USB keyboard and mouse proxies](/doc/usb/) implemented in Qubes. ## What is U2F? @@ -132,4 +131,3 @@ In some cases, you may be the first person to try a particular combination. Consequently (and as with any new feature), users will inevitably encounter bugs. We ask for your patience and understanding in this regard. As always, please [report any bugs you encounter](/doc/issue-tracking/). - diff --git a/user/security-in-qubes/vm-sudo.md b/user/security-in-qubes/vm-sudo.md index 46bff4cf..865f6671 100644 --- a/user/security-in-qubes/vm-sudo.md +++ b/user/security-in-qubes/vm-sudo.md @@ -10,7 +10,6 @@ ref: 165 title: Passwordless Root Access in VMs --- - Background (`/etc/sudoers.d/qubes` in VM): ``` diff --git a/user/security-in-qubes/yubi-key.md b/user/security-in-qubes/yubi-key.md index 50514bb6..10f5809d 100644 --- a/user/security-in-qubes/yubi-key.md +++ b/user/security-in-qubes/yubi-key.md @@ -10,7 +10,6 @@ ref: 169 title: YubiKey --- - You can use a YubiKey to enhance Qubes user authentication, for example to mitigate risk of someone snooping the password. This can also slightly improve security when you have a [USB keyboard](/doc/device-handling-security/#security-warning-on-usb-input-devices). diff --git a/user/templates/debian/debian-upgrade.md b/user/templates/debian/debian-upgrade.md index ae3dd9c4..14eb661d 100644 --- a/user/templates/debian/debian-upgrade.md +++ b/user/templates/debian/debian-upgrade.md @@ -166,4 +166,3 @@ We strongly recommend against using any Debian release that has reached [end-of- * By default, Qubes uses code names in the `apt` sources files, although the templates are referred to by release number. Check the code names for the templates, and ensure you are aware of any changes you have made in the repository definitions. - diff --git a/user/templates/debian/debian.md b/user/templates/debian/debian.md index 022aee11..9c4258a0 100644 --- a/user/templates/debian/debian.md +++ b/user/templates/debian/debian.md @@ -11,7 +11,6 @@ ref: 134 title: Debian Templates --- - The Debian [template](/doc/templates/) is an officially [supported](/doc/supported-versions/#templates) template in Qubes OS. This page is about the standard (or "full") Debian template. For the minimal version, please see the [Minimal templates](/doc/templates/minimal/) page. @@ -110,4 +109,3 @@ The lesson is that you should carefully look at what is being installed to your ### Package installation errors in Qubes 4.0 If some packages throw installation errors, see [this guide.](/doc/vm-troubleshooting/#fixing-package-installation-errors) - diff --git a/user/templates/fedora/fedora-upgrade.md b/user/templates/fedora/fedora-upgrade.md index f0623f10..cf99f773 100644 --- a/user/templates/fedora/fedora-upgrade.md +++ b/user/templates/fedora/fedora-upgrade.md @@ -218,4 +218,3 @@ In this case, you have several options: 3. Do the upgrade in parts, e.g., by using package groups. (First upgrade `@core` packages, then the rest.) 4. Do not perform an in-place upgrade, see [Upgrading Fedora templates](/doc/templates/fedora/#upgrading). - diff --git a/user/templates/fedora/fedora.md b/user/templates/fedora/fedora.md index eedc0150..97725b93 100644 --- a/user/templates/fedora/fedora.md +++ b/user/templates/fedora/fedora.md @@ -6,7 +6,6 @@ ref: 136 title: Fedora Templates --- - The Fedora [template](/doc/templates/) is the default template in Qubes OS. This page is about the standard (or "full") Fedora template. For the minimal and Xfce versions, please see the [Minimal templates](/doc/templates/minimal/) and [Xfce templates](/doc/templates/xfce/) pages. ## Installing @@ -46,4 +45,3 @@ There are two ways to upgrade your template to a new Fedora release: - **Recommended:** [Install a fresh template to replace the existing one.](#installing) **This option may be simpler for less experienced users.** After you install the new template, redo all desired template modifications and [switch everything that was set to the old template to the new template](/doc/templates/#switching). You may want to write down the modifications you make to your templates so that you remember what to redo on each fresh install. To see a log of package manager actions, open a terminal in the old Fedora template and use the `dnf history` command. - **Advanced:** [Perform an in-place upgrade of an existing Fedora template.](/doc/template/fedora/upgrade/) This option will preserve any modifications you've made to the template, **but it may be more complicated for less experienced users.** - diff --git a/user/templates/how-to-reinstall-a-template.md b/user/templates/how-to-reinstall-a-template.md index 0136c16a..9d96bba4 100644 --- a/user/templates/how-to-reinstall-a-template.md +++ b/user/templates/how-to-reinstall-a-template.md @@ -9,7 +9,6 @@ ref: 128 title: How to Reinstall a Template --- - If you suspect your [template](/doc/templates/) is broken, misconfigured, or compromised, you can reinstall any template that was installed from the Qubes repository. Automatic Method @@ -90,4 +89,3 @@ If you want to reinstall more than one template, repeat these instructions for e 6. Delete the cloned template. You can do this in Qubes Manager by right-clicking on the VM and clicking **Remove VM**, or you can use the command `qvm-remove ` in dom0. - diff --git a/user/templates/minimal-templates.md b/user/templates/minimal-templates.md index 4ba56932..0ef2d6cb 100644 --- a/user/templates/minimal-templates.md +++ b/user/templates/minimal-templates.md @@ -353,4 +353,3 @@ Documentation on all of these can be found in the [docs](/doc/). You could, of course, use `qubes-vm-recommended` to automatically install many of these, but in that case you are well on the way to a standard Debian template. - diff --git a/user/templates/xfce-templates.md b/user/templates/xfce-templates.md index 14ad0c13..cc5556b6 100644 --- a/user/templates/xfce-templates.md +++ b/user/templates/xfce-templates.md @@ -11,7 +11,6 @@ ref: 222 title: XFCE Templates --- - If you would like to use Xfce (more lightweight compared to GNOME desktop environment) Linux distribution in your qubes, you can install one of the available Xfce templates for [Fedora](/doc/templates/fedora/), [CentOS](/doc/templates/centos/) or [Gentoo](/doc/templates/gentoo/). @@ -46,4 +45,3 @@ You may wish to try again with the testing repository enabled: The download may take a while depending on your connection speed. To reinstall a Xfce template that is already installed in your system, see [How to Reinstall a template](/doc/reinstall-template/). - diff --git a/user/troubleshooting/disk-troubleshooting.md b/user/troubleshooting/disk-troubleshooting.md index 07a3a516..d10eebea 100644 --- a/user/troubleshooting/disk-troubleshooting.md +++ b/user/troubleshooting/disk-troubleshooting.md @@ -11,7 +11,6 @@ ref: 231 title: Disk Troubleshooting --- - ## "Out of disk space" error ## If the disk is completely full, you will get an `Out of disk space` error that may crash your system because Dom0 does not have enough disk space to work. diff --git a/user/troubleshooting/gui-troubleshooting.md b/user/troubleshooting/gui-troubleshooting.md index 95ee58e4..215fa61b 100644 --- a/user/troubleshooting/gui-troubleshooting.md +++ b/user/troubleshooting/gui-troubleshooting.md @@ -6,7 +6,6 @@ ref: 233 title: GUI Troubleshooting --- - ## Can't click on anything after connecting 4k external display When you connect a 4K external display, you may be unable to click on anything but a small area in the upper-right corner. diff --git a/user/troubleshooting/hardware-troubleshooting.md b/user/troubleshooting/hardware-troubleshooting.md index ab2adda5..7d332f4c 100644 --- a/user/troubleshooting/hardware-troubleshooting.md +++ b/user/troubleshooting/hardware-troubleshooting.md @@ -8,7 +8,6 @@ ref: 97 title: Hardware Troubleshooting --- - ## Audio doesn't work / Troubleshooting newer hardware By default, the kernel that is installed in dom0 comes from the `kernel` package, which is an older Linux LTS kernel. @@ -51,4 +50,3 @@ Restarting `xorg` is required. The most straightforward way is to reboot the system. More information in [this discussion](https://groups.google.com/d/topic/qubes-devel/d8ZQ_62asKI/discussion) and [this GitHub issue](https://github.com/QubesOS/qubes-issues/issues/1396). - diff --git a/user/troubleshooting/hvm-troubleshooting.md b/user/troubleshooting/hvm-troubleshooting.md index 4cafdee3..6f9fc4f0 100644 --- a/user/troubleshooting/hvm-troubleshooting.md +++ b/user/troubleshooting/hvm-troubleshooting.md @@ -6,7 +6,6 @@ ref: 232 title: HVM Troubleshooting --- - ## HVM pauses on boot, followed by kernel error The HVM may pause on boot, showing a fixed cursor. diff --git a/user/troubleshooting/installation-troubleshooting.md b/user/troubleshooting/installation-troubleshooting.md index bcab8981..51fa8b33 100644 --- a/user/troubleshooting/installation-troubleshooting.md +++ b/user/troubleshooting/installation-troubleshooting.md @@ -6,7 +6,6 @@ ref: 224 title: Installation Troubleshooting --- - ## "An unknown error has occurred" error during installation Some people have encountered this error message when trying to install Qubes on drives that already have data on them. @@ -105,4 +104,3 @@ If the setting is not configured correctly, it means that your hardware won’t In Qubes 4.0, the default installation won't function properly without IOMMU, as default sys-net and sys-usb qubes require IOMMU. It is possible to configure them to reduce isolation and not use IOMMU by changing virtualization mode of these two VMs to "PV". In Qubes 4.1, IOMMU is strictly required, even when the virtualization mode of a VM is changed to "PV"; it is not possible to use Qubes on a system without IOMMU. - diff --git a/user/troubleshooting/media-troubleshooting.md b/user/troubleshooting/media-troubleshooting.md index d1bde973..82234b8b 100644 --- a/user/troubleshooting/media-troubleshooting.md +++ b/user/troubleshooting/media-troubleshooting.md @@ -6,7 +6,6 @@ ref: 235 title: Media Troubleshooting --- - ## Can't play media videos in a VM due to missing codecs If you’re having trouble playing a video file in a qube, you’re probably missing the required codecs. diff --git a/user/troubleshooting/pci-troubleshooting.md b/user/troubleshooting/pci-troubleshooting.md index 367dc7d2..18b8f2b8 100644 --- a/user/troubleshooting/pci-troubleshooting.md +++ b/user/troubleshooting/pci-troubleshooting.md @@ -6,7 +6,6 @@ ref: 230 title: PCI Troubleshooting --- - ## DMA errors VMs with attached PCI devices in Qubes have allocated a small buffer for DMA operations (called swiotlb). diff --git a/user/troubleshooting/resume-suspend-troubleshooting.md b/user/troubleshooting/resume-suspend-troubleshooting.md index 4c1e3b54..e44f57da 100644 --- a/user/troubleshooting/resume-suspend-troubleshooting.md +++ b/user/troubleshooting/resume-suspend-troubleshooting.md @@ -9,7 +9,6 @@ ref: 94 title: Suspend/Resume Troubleshooting --- - ## Network-Manager says “Device not ready” on suspend/resume These instructions may help with suspend/resume issues for more devices than just wireless cards, that is just the (unfortunately not uncommon) example used here. diff --git a/user/troubleshooting/uefi-troubleshooting.md b/user/troubleshooting/uefi-troubleshooting.md index c9835556..2ac56fa2 100644 --- a/user/troubleshooting/uefi-troubleshooting.md +++ b/user/troubleshooting/uefi-troubleshooting.md @@ -6,7 +6,6 @@ ref: 177 title: UEFI Troubleshooting --- - ## Successfully installed in legacy mode, but had to change some kernel parameters If you've installed successfully in legacy mode but had to change some kernel parameters for it to work, you should try installing in UEFI mode with the same parameters. diff --git a/user/troubleshooting/update-troubleshooting.md b/user/troubleshooting/update-troubleshooting.md index c2e5b3b1..dc9015b4 100644 --- a/user/troubleshooting/update-troubleshooting.md +++ b/user/troubleshooting/update-troubleshooting.md @@ -6,7 +6,6 @@ ref: 239 title: Update Troubleshooting --- - ## “Failed to synchronize cache for repo” errors when updating Fedora templates This is general Fedora issue, not a Qubes-specific issue. diff --git a/user/troubleshooting/updating-debian-and-whonix.md b/user/troubleshooting/updating-debian-and-whonix.md index ca66338b..9bbf5c9a 100644 --- a/user/troubleshooting/updating-debian-and-whonix.md +++ b/user/troubleshooting/updating-debian-and-whonix.md @@ -6,7 +6,6 @@ ref: 98 title: Updating Debian and Whonix --- - Despite Qubes shipping with [Debian Templates](/doc/templates/debian/), most of Qubes core components run on Fedora and thus our documentation has better coverage for Fedora. However, Qubes has been working closely with the [Whonix](https://whonix.org) project which is based on Debian. This troubleshooting guide is collection of tips about updating Whonix that also pertain to updating the normal Debian package manager. If you plan to use Debian heavily, **we highly recommend you install the Whonix templates and use them to update your normal Debian template.** diff --git a/user/troubleshooting/usb-troubleshooting.md b/user/troubleshooting/usb-troubleshooting.md index 2a20f5ee..24ff7417 100644 --- a/user/troubleshooting/usb-troubleshooting.md +++ b/user/troubleshooting/usb-troubleshooting.md @@ -6,7 +6,6 @@ ref: 234 title: USB Troubleshooting --- - ## disp-sys-usb does not start If the disp-sys-usb does not start, it could be due to a PCI passthrough problem. diff --git a/user/troubleshooting/vm-troubleshooting.md b/user/troubleshooting/vm-troubleshooting.md index 177a6200..d684e8ce 100644 --- a/user/troubleshooting/vm-troubleshooting.md +++ b/user/troubleshooting/vm-troubleshooting.md @@ -8,7 +8,6 @@ ref: 223 title: VM Troubleshooting --- - ## VM Kernel troubleshooting This troubleshoot applies to the non-default kernel choice described in the [Managing VM docs](/doc/managing-vm-kernels/#using-kernel-installed-in-the-vm). diff --git a/user/troubleshooting/vpn-troubleshooting.md b/user/troubleshooting/vpn-troubleshooting.md index 073ba53a..ff223629 100644 --- a/user/troubleshooting/vpn-troubleshooting.md +++ b/user/troubleshooting/vpn-troubleshooting.md @@ -6,7 +6,6 @@ ref: 240 title: VPN Troubleshooting --- - ## Tips * If using qubes-vpn, check the VPN service's log in the VPN VM by running: