summaryrefslogtreecommitdiff
path: root/public_hurd_boxen/domu_console.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'public_hurd_boxen/domu_console.mdwn')
-rw-r--r--public_hurd_boxen/domu_console.mdwn29
1 files changed, 29 insertions, 0 deletions
diff --git a/public_hurd_boxen/domu_console.mdwn b/public_hurd_boxen/domu_console.mdwn
new file mode 100644
index 00000000..56f6ac9c
--- /dev/null
+++ b/public_hurd_boxen/domu_console.mdwn
@@ -0,0 +1,29 @@
+[[!meta copyright="Copyright © 2009 Free Software Foundation, Inc."]]
+
+[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
+id="license" text="Permission is granted to copy, distribute and/or modify this
+document under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no Invariant
+Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
+is included in the section entitled [[GNU Free Documentation
+License|/fdl]]."]]"""]]
+
+[[!meta title="domU console"]]
+
+To avoid any complications with people trying to use the same console at the
+same time, please use this command for attaching to a domU's console:
+
+ $ sudo screen -DRRS xen-console-[domU] xm console [domU]
+
+Otherwise, if one attaches to the same console twice, the second instance will
+in fact forward input to the domU (possibly infering with what the person is
+doing on the first instance), but the output won't be sent back to the second
+instance.
+
+After having typed this once, Bash's `reverse-search-history` (`C-r`), followed
+by typing in `console-flubber`, for example, will be enough to get access to
+that machine's console.
+
+/!\ TODO: How does one get the environment variables `COLUMNS` and `LINES` set
+properly when using `xm console`? This is relevant for everything using
+`(n)curses` -- for interactive console applications.