It's a bit odd to mention ITL here. The original author probably meant
something like "the Qubes developers." (Perhaps the two groups were
coextensive at the time.)
QubesOS#1312
This page is severely out-of-date and has remained so for an extended
period of time, with no one able or willing to update it. The outdated
content has proven misleading or unhelpful to many users. Since we have
nothing with which to replace the outdated content, removing it seems
like the lesser of two evils. (Note that the content is still available
via Git history and other archives for historical reasons and for any
users still on EOL releases.) If anyone is able and willing to
contribute the relevant knowledge and/or text for customizing the
installation of a supported Qubes release, we can bring this page back
in the future.
ClosesQubesOS/qubes-issues#5632ClosesQubesOS/qubes-issues#5637ClosesQubesOS/qubes-issues#7915
- Add new section for 3mdeb MSI PRO Z690-A DDR4
(see QubesOS/qubes-posts#108)
- Rename section from "Qubes-certified laptops" to "Qubes-certified
computers" since the 3mdeb MSI PRO Z690-A DDR4 is not a laptop
- Make descriptions of all certified machines consistent and neutral to
avoid unintentionally biasing readers through choice of language
- Make section headings sentence case
Running “sudo qubes-dom0-update @kde-desktop-qubes” in R4.1 downloads all (at least 276 of them) the packages, but then exits with the message "Module or Group ‘kde-desktop-qubes’ is not available.
Unman suggested $ sudo qubes-dom0-update kde-settings-qubes in the response below, this seems to work properly.
https://forum.qubes-os.org/t/installing-and-running-kde-as-desktop-environment/1513/31
The doc on bind-dirs only provided an example where /var/lib/tor
was made persistent in sys-whonix. However, if one tries to make
persistent any directory that wasn't already present in the
template qube, it would not persist as expected. The issue
QubesOS/qubes-issues#5862 demonstrates this exact confusion.
This commit adds a note about this situation.
FixesQubesOS/qubes-issues#5862
