mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-07-28 09:14:36 -04:00
Merge branch 'main' into toki-newlines
This commit is contained in:
commit
00b72eb890
3 changed files with 7 additions and 9 deletions
|
@ -122,7 +122,7 @@ We recommend consulting these resources when selecting hardware for Qubes OS:
|
||||||
2. The user's OEM, ODM, or MB to provide a suitable BIOS or (U)EFI update for
|
2. The user's OEM, ODM, or MB to provide a suitable BIOS or (U)EFI update for
|
||||||
the user's system.
|
the user's system.
|
||||||
|
|
||||||
Historically, AMD has often been slow to complete step (1), at least for its
|
- Historically, AMD has often been slow to complete step (1), at least for its
|
||||||
client (as opposed to server) platforms. In some cases, AMD has made fixes
|
client (as opposed to server) platforms. In some cases, AMD has made fixes
|
||||||
available for its server platforms very shortly after a security embargo was
|
available for its server platforms very shortly after a security embargo was
|
||||||
lifted, but it did not make fixes available for client platforms facing the
|
lifted, but it did not make fixes available for client platforms facing the
|
||||||
|
@ -132,10 +132,10 @@ We recommend consulting these resources when selecting hardware for Qubes OS:
|
||||||
new CPU vulnerabilities across its supported platforms very shortly after
|
new CPU vulnerabilities across its supported platforms very shortly after
|
||||||
security embargoes have been lifted.
|
security embargoes have been lifted.
|
||||||
|
|
||||||
Step (2) varies by vendor. Many vendors fail to complete step (2) at all,
|
- Step (2) varies by vendor. Many vendors fail to complete step (2) at all,
|
||||||
while some others take a very long time to complete it.
|
while some others take a very long time to complete it.
|
||||||
|
|
||||||
The bottom line is that Qubes OS **can** run on AMD systems, and the Qubes and
|
- The bottom line is that Qubes OS **can** run on AMD systems, and the Qubes and
|
||||||
Xen security teams do their best to provide security support for AMD systems.
|
Xen security teams do their best to provide security support for AMD systems.
|
||||||
However, without the ability to ship microcode updates, there is only so much
|
However, without the ability to ship microcode updates, there is only so much
|
||||||
they can do.
|
they can do.
|
||||||
|
|
|
@ -15,7 +15,7 @@ title: How to copy from dom0
|
||||||
This page covers copying files and clipboard text between [dom0](/doc/glossary/#dom0) and [domUs](/doc/glossary/#domu).
|
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/).
|
Since dom0 is special, the processes are different from [copying and pasting text between qubes](/doc/how-to-copy-and-paste-text/) and [copying and moving files between qubes](/doc/how-to-copy-and-move-files/).
|
||||||
|
|
||||||
## Copying **from** dom0
|
## Copying *from* dom0
|
||||||
|
|
||||||
### Copying files from dom0
|
### Copying files from dom0
|
||||||
|
|
||||||
|
@ -61,7 +61,7 @@ In order to easily copy/paste the contents of logs from dom0 to the inter-VM cli
|
||||||
|
|
||||||
You may now paste the log contents in qube as you normally would (e.g., Ctrl+Shift+V, then Ctrl+V).
|
You may now paste the log contents in qube as you normally would (e.g., Ctrl+Shift+V, then Ctrl+V).
|
||||||
|
|
||||||
## Copying **to** dom0
|
## Copying *to* dom0
|
||||||
|
|
||||||
Copying anything into dom0 is not advised, since doing so can compromise the security of your Qubes system.
|
Copying anything into dom0 is not advised, since doing so can compromise the security of your Qubes system.
|
||||||
For this reason, there is no simple means of copying anything into dom0, unlike [copying from dom0](#copying-from-dom0).
|
For this reason, there is no simple means of copying anything into dom0, unlike [copying from dom0](#copying-from-dom0).
|
||||||
|
|
|
@ -189,13 +189,11 @@ instructions](https://www.debian.org/releases/buster/amd64/release-notes/ch-upgr
|
||||||
|
|
||||||
* If sound is not working, you may need to enable the Qubes testing repository
|
* If sound is not working, you may need to enable the Qubes testing repository
|
||||||
to get the testing version of `qubes-gui-agent`. This can be done by editing
|
to get the testing version of `qubes-gui-agent`. This can be done by editing
|
||||||
the `/etc/apt/sources.list.d/qubes-r4.list` file and uncommenting the `Qubes
|
the `/etc/apt/sources.list.d/qubes-r4.list` file and uncommenting the `Qubes Updates Candidates` repo.
|
||||||
Updates Candidates` repo.
|
|
||||||
|
|
||||||
* User-initiated updates/upgrades may not run when a template first starts.
|
* User-initiated updates/upgrades may not run when a template first starts.
|
||||||
This is due to a new Debian config setting that attempts to update
|
This is due to a new Debian config setting that attempts to update
|
||||||
automatically; it should be disabled with `sudo systemctl disable
|
automatically; it should be disabled with `sudo systemctl disable apt-daily.{service,timer}`.
|
||||||
apt-daily.{service,timer}`.
|
|
||||||
|
|
||||||
Relevant discussions:
|
Relevant discussions:
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue