From 0b40d12439133d6553794a58200ec9b0cba27bad Mon Sep 17 00:00:00 2001
From: Your Name <you@example.com>
Date: Sat, 19 Oct 2019 06:27:02 +0200
Subject: [PATCH 1/2] add documentation for accessing VM console

---
 docs/system/vm-console.md | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)
 create mode 100644 docs/system/vm-console.md

diff --git a/docs/system/vm-console.md b/docs/system/vm-console.md
new file mode 100644
index 0000000..cc38e68
--- /dev/null
+++ b/docs/system/vm-console.md
@@ -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.

From 4c4ef2d00bac6c2e5c89797e3751c481e2f3d2b2 Mon Sep 17 00:00:00 2001
From: tetrahedras <tetrahedrass>
Date: Sat, 19 Oct 2019 06:46:38 +0200
Subject: [PATCH 2/2] add terminal defaults howto as per issue #73

---
 docs/README.md                          |  1 +
 docs/customization/terminal-defaults.md | 29 +++++++++++++++++++++++++
 2 files changed, 30 insertions(+)
 create mode 100644 docs/customization/terminal-defaults.md

diff --git a/docs/README.md b/docs/README.md
index fbb3b4e..cabee97 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -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)
diff --git a/docs/customization/terminal-defaults.md b/docs/customization/terminal-defaults.md
new file mode 100644
index 0000000..f71276d
--- /dev/null
+++ b/docs/customization/terminal-defaults.md
@@ -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.
+