mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-03-13 02:06:29 -04:00
small formatting issues
This commit is contained in:
parent
cb1f45fe97
commit
8085719b1c
@ -109,6 +109,7 @@ Note that if the request is redirected (`target=` parameter), policy action rema
|
||||
If no policy rule is matched, the action is denied.
|
||||
|
||||
In the target VM, a file in either of the following locations must exist, containing the file name of the program that will be invoked, or being that program itself -- in which case it must have executable permission set (`chmod +x`):
|
||||
|
||||
- `/etc/qubes-rpc/RPC_ACTION_NAME` when you make it in the template qube;
|
||||
- `/usr/local/etc/qubes-rpc/RPC_ACTION_NAME` for making it only in an app qube.
|
||||
|
||||
|
@ -21,7 +21,7 @@ qvm-features dom0 gui-videoram-min $(($WIDTH * $HEIGHT * 4 / 1024))
|
||||
qvm-features dom0 gui-videoram-overhead 0
|
||||
```
|
||||
|
||||
Where `$WIDTH`×`$HEIGHT` is the maximum desktop size that you anticipate needing.
|
||||
Where `$WIDTH` × `$HEIGHT` is the maximum desktop size that you anticipate needing.
|
||||
For example, if you expect to use a 1080p display and a 4k display side-by-side, that is `(1920 + 3840) × 2160 × 4 / 1024 = 48600`, or slightly more than 48 MiB per qube.
|
||||
After making these adjustments, the qubes need to be restarted.
|
||||
|
||||
|
@ -43,7 +43,7 @@ This is how we create a policy that says: "VMs tagged with 'work' are allowed to
|
||||
|
||||
When an operation is initiated with a specific target, e.g. `qvm-copy-to-vm other_work_vm some_file` the policy mechanism looks for a row
|
||||
matching `source_work_vm other_work_vm PERMISSION`. In this case, assuming both VMs have the `work` tag, the second row would match, and
|
||||
the operation would be `allow`ed without any prompts. When an operation is initiated without a specific target, e.g. `qvm-copy some_file`,
|
||||
the operation would be `allow`-ed without any prompts. When an operation is initiated without a specific target, e.g. `qvm-copy some_file`,
|
||||
the policy mechanism looks for a row matching `source_work_vm @default PERMISSION`. In this case, the first row indicates that the user
|
||||
should be prompted for the destination. The list of destination VMs in the prompt is filtered to only include VMs that are valid as per
|
||||
the policy (so in this example, only other work VMs would be listed). If the first row was commented out, the second row would not match
|
||||
|
Loading…
x
Reference in New Issue
Block a user