mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-12-11 06:01:51 -05:00
Change URIs from CamelCase to lowercase-hyphen-separated
This commit is contained in:
Axon
parent
bb5fb46527
commit
f3ee78f223
160 changed files with 888 additions and 579 deletions
|
|
@ -1,14 +1,16 @@
|
|||
---
|
||||
layout: doc
|
||||
title: FedoraTemplateUpgrade
|
||||
permalink: /doc/FedoraTemplateUpgrade18/
|
||||
redirect_from: /wiki/FedoraTemplateUpgrade/
|
||||
permalink: /en/doc/fedora-template-upgrade-18/
|
||||
redirect_from:
|
||||
- /doc/FedoraTemplateUpgrade18/
|
||||
- /wiki/FedoraTemplateUpgrade/
|
||||
---
|
||||
|
||||
Upgrade of Fedora template
|
||||
==========================
|
||||
|
||||
(**Note:** There is a [newer version of this page for upgrading from Fedora 20 to Fedora 21](/doc/FedoraTemplateUpgrade20/).)
|
||||
(**Note:** There is a [newer version of this page for upgrading from Fedora 20 to Fedora 21](/en/doc/fedora-template-upgrade-20/).)
|
||||
|
||||
This instruction in simplified version of [official Fedora instruction](https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum). Note that only "yum" method will work in Qubes template VM (if you are curious why: mostly because template VM does not have own bootloader).
|
||||
|
||||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: FedoraTemplateUpgrade
|
||||
permalink: /doc/FedoraTemplateUpgrade20/
|
||||
redirect_from: /wiki/FedoraTemplateUpgrade20/
|
||||
permalink: /en/doc/fedora-template-upgrade-20/
|
||||
redirect_from:
|
||||
- /doc/FedoraTemplateUpgrade20/
|
||||
- /wiki/FedoraTemplateUpgrade20/
|
||||
---
|
||||
|
||||
How to Upgrade Fedora Templates
|
||||
|
|
@ -195,7 +197,7 @@ As mentioned above, you may encounter the following `yum` error:
|
|||
|
||||
In this case, you have several options:
|
||||
|
||||
1. [Increase the TemplateVM's disk image size](/doc/ResizeDiskImage/).
|
||||
1. [Increase the TemplateVM's disk image size](/en/doc/resize-disk-image/).
|
||||
This is the solution mentioned in the main instructions above.
|
||||
2. Delete files in order to free up space. One way to do this is by
|
||||
uninstalling packages. You may then reinstalling them again after you
|
||||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: HvmCreate
|
||||
permalink: /doc/HvmCreate/
|
||||
redirect_from: /wiki/HvmCreate/
|
||||
permalink: /en/doc/hvm-create/
|
||||
redirect_from:
|
||||
- /doc/HvmCreate/
|
||||
- /wiki/HvmCreate/
|
||||
---
|
||||
|
||||
Creating and using HVM (fully virtualized) domains in Qubes 2
|
||||
|
|
@ -193,12 +195,12 @@ In the near future we plan on introducing shared template also for HVM domains,
|
|||
~~Installing Qubes support tools in Windows 7 VMs~~ (only for R2 Beta 2)
|
||||
------------------------------------------------------------------------
|
||||
|
||||
Note: the R2 Beta 3 (which is coming soon) has automated most of the actions described below -- please see [this page instead](/doc/WindowsAppVms/).
|
||||
Note: the R2 Beta 3 (which is coming soon) has automated most of the actions described below -- please see [this page instead](/en/doc/windows-appvms/).
|
||||
|
||||
Qubes support tools for Windows VMs is a set of programs and drivers that provide integration of Windows VMs with the rest of the Qubes system. Currently the following features become available for Windows VMs after installation of those tools:
|
||||
|
||||
- Support for [secure clipboard copy/paste](/doc/CopyPaste/) between the Windows VM and other AppVMs
|
||||
- Support for [secure file exchange](/doc/CopyingFiles/) between the Windows VM and other AppVMs
|
||||
- Support for [secure clipboard copy/paste](/en/doc/copy-paste/) between the Windows VM and other AppVMs
|
||||
- Support for [secure file exchange](/en/doc/copying-files/) between the Windows VM and other AppVMs
|
||||
- Support for qvm-run and generic qrexec for the Windows VM (e.g. ability to run custom service within/from the Windows VM)
|
||||
- Xen PV drivers for Windows that increase performance compared to qemu emulated devices
|
||||
|
||||
|
|
@ -294,7 +296,7 @@ And the screenshot below illustrates the Send To entries in a Windows VM that ca
|
|||
Assigning PCI devices to HVM domains
|
||||
------------------------------------
|
||||
|
||||
HVM domains (including Windows VMs) can be [assigned PCI devices](/doc/AssigningDevices/) just like normal AppVMs. E.g. one can assign one of the USB controllers to the Windows VM and should be able to use various devices that require Windows software, such as phones, electronic devices that are configured via FTDI, etc.
|
||||
HVM domains (including Windows VMs) can be [assigned PCI devices](/en/doc/assigning-devices/) just like normal AppVMs. E.g. one can assign one of the USB controllers to the Windows VM and should be able to use various devices that require Windows software, such as phones, electronic devices that are configured via FTDI, etc.
|
||||
|
||||
Once problem, however, at the moment, is that after the whole system gets suspend into S3 sleep, and subsequently resumed, such attached devices stop working and should be restarted within the VM. Under Windows this can be achieved by opening the Device Manager, selecting the actual device, such as a USB controller, and then first 'Disabling', and then 'Enabling' the device again. This is illustrated on the screenshot below:
|
||||
|
||||
|
|
@ -305,5 +307,5 @@ Further reading
|
|||
|
||||
Other documents related to HVM:
|
||||
|
||||
- [LinuxHVMTips](/doc/LinuxHVMTips/)
|
||||
- [LinuxHVMTips](/en/doc/linux-hvm-tips/)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: LinuxHVMTips
|
||||
permalink: /doc/LinuxHVMTips/
|
||||
redirect_from: /wiki/LinuxHVMTips/
|
||||
permalink: /en/doc/linux-hvm-tips/
|
||||
redirect_from:
|
||||
- /doc/LinuxHVMTips/
|
||||
- /wiki/LinuxHVMTips/
|
||||
---
|
||||
|
||||
Tips for Linux in HVM domain
|
||||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: Templates
|
||||
permalink: /doc/Templates/
|
||||
redirect_from: /wiki/Templates/
|
||||
permalink: /en/doc/templates/
|
||||
redirect_from:
|
||||
- /doc/Templates/
|
||||
- /wiki/Templates/
|
||||
---
|
||||
|
||||
Templates
|
||||
|
|
@ -15,7 +17,7 @@ additional software installed by default. This concept is described
|
|||
[here](/doc/GettingStarted/#appvms-domains-and-templatevms).
|
||||
|
||||
Some templates are available in ready to use binary form, but some of them are
|
||||
only as a source code, which can be built using [Qubes Builder](/doc/QubesBuilder/).
|
||||
only as a source code, which can be built using [Qubes Builder](/en/doc/qubes-builder/).
|
||||
Especially some templates "flavors" are available in source code form only.
|
||||
Take a look at [Qubes Builder
|
||||
documentation](https://github.com/QubesOS/qubes-builder/blob/master/README.md)
|
||||
|
|
@ -30,7 +32,7 @@ the source code we publish.
|
|||
|
||||
- Fedora
|
||||
- [Fedora - Minimal](/doc/Templates/FedoraMinimal)
|
||||
- [Debian](/doc/Templates/Debian/)
|
||||
- [Debian](/en/doc/templates/debian/)
|
||||
|
||||
Community Supported templates
|
||||
-----------------------------
|
||||
|
|
@ -44,7 +46,7 @@ In short - by installing those templates, you trust not only ITL and
|
|||
distribution maintainers, but also the template maintainer. It can also happen
|
||||
that those templates are somehow less stable, because we do not test them.
|
||||
|
||||
- [Whonix](/doc/Templates/Whonix/)
|
||||
- [Ubuntu](/doc/Templates/Ubuntu/)
|
||||
- [Archlinux](/doc/Templates/Archlinux/)
|
||||
- [Whonix](/en/doc/templates/whonix/)
|
||||
- [Ubuntu](/en/doc/templates/ubuntu/)
|
||||
- [Archlinux](/en/doc/templates/archlinux/)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: Archlinux template
|
||||
permalink: /doc/Templates/Archlinux/
|
||||
redirect_from: /wiki/Templates/Archlinux/
|
||||
permalink: /en/doc/templates/archlinux/
|
||||
redirect_from:
|
||||
- /doc/Templates/Archlinux/
|
||||
- /wiki/Templates/Archlinux/
|
||||
---
|
||||
|
||||
Archlinux template
|
||||
|
|
@ -25,7 +27,7 @@ Install
|
|||
-------
|
||||
|
||||
Currently we do not ship ready to use binary package. It can be compiled using
|
||||
[this instructions](/doc/BuildingArchlinuxTemplate/).
|
||||
[this instructions](/en/doc/building-archlinux-template/).
|
||||
|
||||
Olivier provides binary package build by himself, you can get it for:
|
||||
* Qubes R2 [here](https://groups.google.com/d/msgid/qubes-devel/54CE3FB1.3050708%40yahoo.fr).
|
||||
|
|
@ -36,4 +38,4 @@ Olivier provides binary package build by himself, you can get it for:
|
|||
Known issues
|
||||
------------
|
||||
|
||||
If you want to help in improving the template, feel free to [contribute](/doc/ContributingHowto/).
|
||||
If you want to help in improving the template, feel free to [contribute](/en/doc/contributing/).
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: Debian
|
||||
permalink: /doc/Templates/Debian/
|
||||
redirect_from: /wiki/Templates/Debian/
|
||||
permalink: /en/doc/templates/debian/
|
||||
redirect_from:
|
||||
- /doc/Templates/Debian/
|
||||
- /wiki/Templates/Debian/
|
||||
---
|
||||
|
||||
Debian template(s)
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: FedoraMinimal
|
||||
permalink: /doc/Templates/FedoraMinimal/
|
||||
redirect_from: /wiki/Templates/FedoraMinimal/
|
||||
permalink: /en/doc/templates/fedora-minimal/
|
||||
redirect_from:
|
||||
- /doc/Templates/FedoraMinimal/
|
||||
- /wiki/Templates/FedoraMinimal/
|
||||
---
|
||||
|
||||
Fedora - minimal
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: Ubuntu
|
||||
permalink: /doc/Templates/Ubuntu/
|
||||
redirect_from: /wiki/Templates/Ubuntu/
|
||||
permalink: /en/doc/templates/ubuntu/
|
||||
redirect_from:
|
||||
- /doc/Templates/Ubuntu/
|
||||
- /wiki/Templates/Ubuntu/
|
||||
---
|
||||
|
||||
Ubuntu template(s)
|
||||
|
|
@ -18,7 +20,7 @@ to redistribute a modified Ubuntu. The redistribution is not allowed by their
|
|||
Install
|
||||
-------
|
||||
|
||||
It can built using [Qubes Builder](/doc/QubesBuilder/). You can also access its
|
||||
It can built using [Qubes Builder](/en/doc/qubes-builder/). You can also access its
|
||||
documentation in the [source code
|
||||
repository](https://github.com/QubesOS/qubes-builder/blob/master/README.md).
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: Whonix template
|
||||
permalink: /doc/Templates/Whonix/
|
||||
redirect_from: /wiki/Templates/Whonix/
|
||||
permalink: /en/doc/templates/whonix/
|
||||
redirect_from:
|
||||
- /doc/Templates/Whonix/
|
||||
- /wiki/Templates/Whonix/
|
||||
---
|
||||
|
||||
Whonix template(s)
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: UninstallingWindowsTools2
|
||||
permalink: /doc/UninstallingWindowsTools2/
|
||||
redirect_from: /wiki/UninstallingWindowsTools2/
|
||||
permalink: /en/doc/uninstalling-windows-tools-2/
|
||||
redirect_from:
|
||||
- /doc/UninstallingWindowsTools2/
|
||||
- /wiki/UninstallingWindowsTools2/
|
||||
---
|
||||
|
||||
Uninstalling Qubes Tools for Windows v2.x
|
||||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: WindowsAppVms
|
||||
permalink: /doc/WindowsAppVms/
|
||||
redirect_from: /wiki/WindowsAppVms/
|
||||
permalink: /en/doc/windows-appvms/
|
||||
redirect_from:
|
||||
- /doc/WindowsAppVms/
|
||||
- /wiki/WindowsAppVms/
|
||||
---
|
||||
|
||||
Installing and using Windows-based AppVMs
|
||||
|
|
@ -13,8 +15,8 @@ Qubes provides special support for running Windows-based AppVMs. This requires t
|
|||
Qubes support tools for Windows is a set of programs and drivers that provide integration of Windows AppVMs with the rest of the Qubes system. Currently the following features are available for Windows VMs after installation of those tools:
|
||||
|
||||
- Seamless GUI mode that integrates apps windows onto the common Qubes trusted desktop (available on Qubes R2 Beta 3 and later)
|
||||
- Support for [secure clipboard copy/paste](/doc/CopyPaste/) between the Windows VM and other AppVMs
|
||||
- Support for [secure file exchange](/doc/CopyingFiles/) between the Windows VM and other AppVMs
|
||||
- Support for [secure clipboard copy/paste](/en/doc/copy-paste/) between the Windows VM and other AppVMs
|
||||
- Support for [secure file exchange](/en/doc/copying-files/) between the Windows VM and other AppVMs
|
||||
- Support for qvm-run and generic qrexec for the Windows VM (e.g. ability to run custom service within/from the Windows VM)
|
||||
- Xen PV drivers for Windows that increase performance compared to qemu emulated devices
|
||||
|
||||
|
|
@ -25,7 +27,7 @@ NOTE: Currently only 64-bit versions of Windows 7 are support by Qubes Windows T
|
|||
Installing Windows OS in a Qubes VM
|
||||
-----------------------------------
|
||||
|
||||
Please refer to [this page](/doc/HvmCreate/) for instructions on how to install Windows in a Qubes VM.
|
||||
Please refer to [this page](/en/doc/hvm-create/) for instructions on how to install Windows in a Qubes VM.
|
||||
|
||||
Installing Qubes support tools in Windows 7 VMs
|
||||
-----------------------------------------------
|
||||
|
|
@ -101,7 +103,7 @@ Qubes allows HVM VMs to share a common root filesystem from a select Template VM
|
|||
qvm-create --hvm-template win7-x64-template -l green
|
||||
~~~
|
||||
|
||||
... and install Windows OS (or other OS) into this template the same way as you would install it into a normal HVM -- please see [this page](/doc/HvmCreate/) instructions. However, it would make lots of sense to store the `C:\Users` directory on the 2nd disk which is automatically exposed by Qubes to all HVMs. This 2nd disk is backed by the `private.img` file in the AppVMs' and is not reset upon AppVMs reboot, so the user's directories and profiles would survive the AppVMs reboot, unlike the "root" filesystem which will be reverted to the "golden image" from the Template VM automatically. To facilitate such separation of user profiles, Qubes Windows Tools provide an option to automatically move `C:\Users` directory to the 2nd disk backed by `private.img`. It's a selectable feature of the installer, enabled by default. If that feature is selected during installation, completion of the process requires two reboots:
|
||||
... and install Windows OS (or other OS) into this template the same way as you would install it into a normal HVM -- please see [this page](/en/doc/hvm-create/) instructions. However, it would make lots of sense to store the `C:\Users` directory on the 2nd disk which is automatically exposed by Qubes to all HVMs. This 2nd disk is backed by the `private.img` file in the AppVMs' and is not reset upon AppVMs reboot, so the user's directories and profiles would survive the AppVMs reboot, unlike the "root" filesystem which will be reverted to the "golden image" from the Template VM automatically. To facilitate such separation of user profiles, Qubes Windows Tools provide an option to automatically move `C:\Users` directory to the 2nd disk backed by `private.img`. It's a selectable feature of the installer, enabled by default. If that feature is selected during installation, completion of the process requires two reboots:
|
||||
|
||||
- The private disk is initialized and formatted on the first reboot after tools installation. It can't be done **during** the installation because Xen mass storage drivers are not yet active.
|
||||
- User profiles are moved to the private disk on the next reboot after the private disk is initialized. Reboot is required because the "mover utility" runs very early in the boot process so OS can't yet lock any files in there. This can take some time depending on the profiles' size and because the GUI agent is not yet active dom0/Qubes Manager may complain that the AppVM failed to boot. That's a false alarm (you can increase AppVM's default boot timeout using `qvm-prefs`), the VM should appear "green" in Qubes Manager shortly after.
|
||||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: WindowsTools2
|
||||
permalink: /doc/WindowsTools2/
|
||||
redirect_from: /wiki/WindowsTools2/
|
||||
permalink: /en/doc/windows-tools-2/
|
||||
redirect_from:
|
||||
- /doc/WindowsTools2/
|
||||
- /wiki/WindowsTools2/
|
||||
---
|
||||
|
||||
Qubes Tools for Windows: advanced settings and troubleshooting
|
||||
|
|
@ -34,7 +36,7 @@ If the install process fails you can retry it using the command line below to ge
|
|||
Uninstalling
|
||||
------------
|
||||
|
||||
See [this page](/doc/UninstallingWindowsTools2/).
|
||||
See [this page](/en/doc/uninstalling-windows-tools-2/).
|
||||
|
||||
Configuration
|
||||
-------------
|
||||
|
|
@ -1,9 +1,13 @@
|
|||
---
|
||||
layout: doc
|
||||
title: WindowsTools
|
||||
permalink: /doc/WindowsTools3/
|
||||
redirect_from: /wiki/WindowsTools/
|
||||
redirect_from: /doc/WindowsTools/
|
||||
permalink: /en/doc/windows-tools-3/
|
||||
redirect_from:
|
||||
- /doc/WindowsTools3/
|
||||
- /wiki/WindowsTools/
|
||||
redirect_from:
|
||||
-
|
||||
- /doc/WindowsTools/
|
||||
---
|
||||
|
||||
Qubes Tools for Windows: advanced settings and troubleshooting
|
||||
Loading…
Add table
Add a link
Reference in a new issue