Git-Mirrors/Qubes-Community-Content
1
0
Fork 0
mirror of https://github.com/Qubes-Community/Contents.git synced 2024-12-23 06:09:29 -05:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #75 from tetrahedras/terminal-defaults

Browse Source 
Add files in as per #73.
This commit is contained in:
awokd 2019-10-19 11:50:22 +00:00 committed by GitHub
commit 15fbaaf510
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 49 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/README.md
View File

@ -24,6 +24,7 @@
- [setup mirage firewall](customization/mirage-firewall.md)
- [windows 7 gaming HVM with GPU passthrough](customization/windows-gaming-hvm.md)
- [SecBrowser "security-enhanced" browser](customization/secbrowser.md)
- [Choose deafult terminal settings for a TemplateVM](customization/terminal-defaults.md)
`hardware`
- [tips on choosing the right hardware](hardware/hardware-selection.md)

29
docs/customization/terminal-defaults.md Normal file
View File

@ -0,0 +1,29 @@
# Setting default terminal settings for a TemplateVM
When you create a VM based on a TemplateVM, the `gnome-terminal` settings (font, color) are not inherited by default. This document describes how to set terminal defaults for all VMs *subsequently* created off a TemplateVM.
(Previously-created VMs are unaffected.)
This document only applies to `gnome-terminal` (the standard terminal)
and not XTerm, etc.
Thanks to `unman` on qubes-users for explaining how to do this.
## Define your defaults
In dom0:
`qvm-run MYTEMPLATE gnome-terminal`
In the terminal that pops up, adjust settings to your liking.
## Save settings template-wide
In the templateVM's terminal:
```
sudo mkdir -p /etc/skel/.config/dconf
sudo cp ~/.config/dconf/user /etc/skel/.config/dconf/
sudo reboot
```
Subsequently-created VMs should now use the chosen settings by default.

19
docs/system/vm-console.md Normal file
View File

@ -0,0 +1,19 @@
# Connect to a VM console
In some cases it's not possible to use a standard graphical terminal emulator to interact with a VM. In this case, "serial console" access is still available using two tools.
## qvm-console-dispvm
Usage: `qvm-console-dispvm VMNAME`
Launches a DispVM connected to the VM's console, using the qubes.ShowInTerminal RPC service. This provides a full-featured console.
At the time of writing this command contains a bug whose fix is waiting on release, therefore it may be necessary to use the following.
## xl console
Usage: `sudo xl console VMNAME`
Uses Xenlight to directly access the VM console from dom0. For [security reasons](https://github.com/QubesOS/qubes-vmm-xen/blob/xen-4.8/patch-tools-xenconsole-replace-ESC-char-on-xenconsole-outp.patch) this console is deliberately limited in what it can display.
Line-by-line text will work fine, but if a Curses-style pseudo-graphical-interface comes up the output will be garbled and you will need a tool like [asciinema](https://asciinema.org/) to untangle it.