mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-07-23 23:11:25 -04:00
Update attachment paths
This commit is contained in:
Andrew David Wong
parent
ba376404e0
commit
e5a21f7488
30 changed files with 107 additions and 107 deletions
|
|
@ -31,7 +31,7 @@ Due to its overarching importance, dom0 has no network connectivity and is used
|
|||
|
||||
You'll choose a **color** for each of your qubes out of a predefined set of colors. Each window on your desktop will have its frame colored according to the color of that qube. These colored frames help you keep track of which qube each window belongs to and how trustworthy it is. This is especially helpful when you have the same app running in multiple qubes at the same time. For example, if you're logged in to your bank account in one qube while doing some random web surfing in a different qube, you wouldn't want to accidentally enter your banking password in the latter! The colored frames help to avoid such mistakes.
|
||||
|
||||
[](/attachment/wiki/GettingStarted/r4.0-snapshot_40.png)
|
||||
[
|
||||
|
||||
Most Qubes users associate red with what's untrusted and dangerous (like a red light: stop! danger!), green with what's safe and trusted, and yellow and orange with things in the middle. This color scheme also extends to include blue and black, which are usually interpreted as indicating progressively more trusted domains than green, with black being ultimately trusted.
|
||||
Color and associated meanings are ultimately up to you, however. The system itself does not treat the colors differently. If you create two identical qubes --- black and red, say --- they'll be the same until you start using them differently. Feel free to use the colors in whatever way is most useful to you. For example, you might decide to use three or four qubes for work activities and give them all the same color --- or all different colors. It's entirely up to you.
|
||||
|
|
@ -40,7 +40,7 @@ Color and associated meanings are ultimately up to you, however. The system itse
|
|||
|
||||
On operating systems like Windows and macOS, the desktop environment is unchangeable and part of that operating system. With Linux, any of a number of desktop environments are an option. Qubes OS is installed with XFCE as its default desktop environment, but it also supports KDE, as well as the i3 and awesome window managers.
|
||||
|
||||
[](/attachment/wiki/GettingStarted/r4.0-taskbar.png)
|
||||
[
|
||||
|
||||
The bar at the top of your screen in Qubes 4.0 includes the following XFCE component areas:
|
||||
|
||||
|
|
@ -58,11 +58,11 @@ There are several Tray widgets that are custom to Qubes OS:
|
|||
- The **Qubes Disk Space Monitor** will notify you if you're ever running out of disk space.
|
||||
- The **Qubes Update** tool will inform you when updates are available.
|
||||
|
||||
[](/attachment/wiki/GettingStarted/r4.0-q40_widgets.png)
|
||||
[
|
||||
|
||||
To see all of your qubes at the same time, you can use the **Qube Manager** (go to the App Menu → System Tools → Qube Manager), which displays the states of all the qubes in your system, even the ones that aren't running.
|
||||
|
||||
[](/attachment/wiki/GettingStarted/r4.0-qubes-manager.png)
|
||||
[
|
||||
|
||||
#### Command-line interface
|
||||
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ To permanently install new software in a template:
|
|||
These new shortcuts will appear in the Applications Menu.
|
||||
(If you encounter problems, see [here](/doc/app-menu-shortcut-troubleshooting/) for troubleshooting.)
|
||||
|
||||
](/attachment/wiki/ManagingAppVmShortcuts/r4.1-dom0-appmenu-select.png)
|
||||
|
||||
|
||||
## How to update software
|
||||
|
||||
|
|
|
|||
|
|
@ -38,11 +38,11 @@ Fully updating your Qubes OS system means updating:
|
|||
|
||||
You can accomplish this using the **Qubes Update** tool.
|
||||
|
||||
[](/attachment/wiki/QubesScreenshots/r4.0-software-update.png)
|
||||
[
|
||||
|
||||
By default, the Qubes Update tool will appear as an icon in the Notification Area when updates are available.
|
||||
|
||||
[](/attachment/wiki/QubesScreenshots/r4.0-qube-updates-available.png)
|
||||
[
|
||||
|
||||
However, you can also start the tool manually by selecting it in the Applications Menu under "System Tools."
|
||||
Even if no updates have been detected, you can use this tool to check for updates manually at any time by selecting "Enable updates for qubes without known available updates," then selecting all desired items from the list and clicking "Next."
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ In addition to smaller flash memory sticks, this includes things like USB extern
|
|||
|
||||
Qubes OS supports the ability to attach a USB drive (or just its partitions) to any qube easily, no matter which qube handles the USB controller.
|
||||
|
||||
Attaching USB drives is integrated into the Devices Widget: 
|
||||
Attaching USB drives is integrated into the Devices Widget: 
|
||||
Simply insert your USB drive and click on the widget.
|
||||
You will see multiple entries for your USB drive; typically, `sys-usb:sda`, `sys-usb:sda1`, and `sys-usb:2-1` for example.
|
||||
Entries starting with a number (e.g. here `2-1`) are the [whole usb-device](/doc/how-to-use-usb-devices/).
|
||||
|
|
@ -178,7 +178,7 @@ To attach a file as block device to another qube, first turn it into a loopback
|
|||
Afterwards it prints the device-node-name it found.
|
||||
|
||||
2. If you want to use the GUI, you're done.
|
||||
Click the Device Manager  and select the `loop0`-device to attach it to another qube.
|
||||
Click the Device Manager  and select the `loop0`-device to attach it to another qube.
|
||||
|
||||
If you rather use the command line, continue:
|
||||
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ PCI devices can be attached using the Qube Settings, but require a VM reboot.
|
|||
|
||||
## General Qubes Device Widget Behavior And Handling ##
|
||||
|
||||
When clicking on the tray icon (which looks similar to this):  several device-classes separated by lines are displayed as tooltip.
|
||||
When clicking on the tray icon (which looks similar to this):  several device-classes separated by lines are displayed as tooltip.
|
||||
Block devices are displayed on top, microphones one below and USB-devices at the bottom.
|
||||
|
||||
On most laptops, integrated hardware such as cameras and fingerprint-readers are implemented as USB-devices and can be found here.
|
||||
|
|
@ -57,7 +57,7 @@ Click on one and your device will be attached!
|
|||
To detach a device, click the Qubes Devices Widget icon again.
|
||||
Attached devices are displayed in bold.
|
||||
Hover the one you want to detach.
|
||||
A list of VMs appears, one showing the eject symbol: 
|
||||
A list of VMs appears, one showing the eject symbol: 
|
||||
|
||||
|
||||
### Attaching a Device to Several VMs ###
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ This means that you can safely work with untrusted files without risk of comprom
|
|||
disposables can be launched either directly from dom0's Start Menu or terminal window, or from within app qubes.
|
||||
While running, disposables will appear in Qubes VM Manager with the name `disp####`.
|
||||
|
||||
[](/attachment/wiki/DisposableVms/disposablevm-example.png)
|
||||
[
|
||||
|
||||
This diagram provides a general example of how disposables can be used to safely open untrusted links and attachments in disposables. See [this article](https://blog.invisiblethings.org/2010/06/01/disposable-vms.html) for more on why one would want to use a disposable.
|
||||
|
||||
|
|
@ -102,7 +102,7 @@ This app is running in its own dedicated VM -- a disposable created for the purp
|
|||
Once you close the viewing application the whole disposable will be destroyed.
|
||||
If you have edited the file and saved the changes, the changed file will be saved back to the original app qube, overwriting the original.
|
||||
|
||||
 
|
||||
|
||||
|
||||
|
||||
## Opening a fresh web browser instance in a new disposable
|
||||
|
|
@ -112,7 +112,7 @@ This can be done easily using the Start Menu: just go to **Application Menu -\>
|
|||
Wait a few seconds until a web browser starts.
|
||||
Once you close the viewing application the whole disposable will be destroyed.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Opening a file in a disposable via command line (from app qube)
|
||||
|
|
|
|||
|
|
@ -45,7 +45,7 @@ There you can attach PCI-devices to a qube.
|
|||
|
||||
1. To reach the settings of any qube either
|
||||
|
||||
- Press Alt+F3 to open the application finder, type in the VM name, select the "\[VM-name\]: Qube Settings" menu entry and press enter or click "Launch"!
|
||||
- Press Alt+F3 to open the application finder, type in the VM name, select the "\[VM-name\]: Qube Settings" menu entry and press enter or click "Launch"!
|
||||
- Select the VM in Qube Manager and click the settings-button or right-click the VM and select `Qube settings`.
|
||||
- Click the Domain Manager, hover the VM you want to attach a device to and select "settings" in the additional menu. (only running VMs!)
|
||||
|
||||
|
|
|
|||
|
|
@ -33,9 +33,9 @@ But it has some [issues](https://github.com/QubesOS/qubes-issues/issues/4661).)
|
|||
|
||||
### With Qubes Device Manager
|
||||
|
||||
Click the device-manager-icon: 
|
||||
Click the device-manager-icon: 
|
||||
A list of available devices appears.
|
||||
USB-devices have a USB-icon to their right: 
|
||||
USB-devices have a USB-icon to their right: 
|
||||
|
||||
Hover on one device to display a list of VMs you may attach it to.
|
||||
|
||||
|
|
@ -46,7 +46,7 @@ You're done.
|
|||
After you finished using the USB-device, you can detach it the same way by clicking on the Devices Widget.
|
||||
You will see an entry in bold for your device such as **`sys-usb:2-5 - 058f_USB_2.0_Camera`**.
|
||||
Hover on the attached device to display a list of running VMs.
|
||||
The one to which your device is connected will have an eject button  next to it.
|
||||
The one to which your device is connected will have an eject button  next to it.
|
||||
Click that and your device will be detached.
|
||||
|
||||
### With The Command Line Tool
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue