Editing X inside VE
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 5: | Line 5: | ||
=== Single application === | === Single application === | ||
− | To run an X application inside a [[container]], one | + | To run an X application inside a [[container]], one need simply to connect to a container with '''ssh -X''': |
<pre> | <pre> | ||
host# ssh -2 -c blowfish -X user@address | host# ssh -2 -c blowfish -X user@address | ||
Line 100: | Line 100: | ||
Change your display settings (don't forget to change them back after you establish a connection) | Change your display settings (don't forget to change them back after you establish a connection) | ||
− | <pre>DISPLAY=:1 | + | <pre>DISPLAY=:1,0</pre> |
Forward your application or desktop over ssh to Xephyr | Forward your application or desktop over ssh to Xephyr | ||
Line 140: | Line 140: | ||
===== GDM ===== | ===== GDM ===== | ||
− | Edit the '''gdm.conf''' file and in xdmcp section, comment out the | + | Edit the '''gdm.conf''' file and in xdmcp section, comment out the 0=standard line under the [servers] section - this will prevent gdm from trying to launch an X server on the local machine - it will simply listen for xdmcp requests. Also, change from VCAllocation=true to VTAllocation=false and comment out the FirstVT=7 line. Change the access restrictions (if any) to suit your needs and then start GDM. |
=== Client/Host Configuration === | === Client/Host Configuration === | ||
Line 152: | Line 152: | ||
=== Errata === | === Errata === | ||
On a side note, as of December 2007, I was never able to successfully get an Xserver to run inside a container and have the display output onto virtual-terminal 7 (the Xserver default), However, you can get an Xserver running on the hostnode to display output on virtual-terminal 7 without any special configuration (as the hostnode has direct access to all necessary devices). | On a side note, as of December 2007, I was never able to successfully get an Xserver to run inside a container and have the display output onto virtual-terminal 7 (the Xserver default), However, you can get an Xserver running on the hostnode to display output on virtual-terminal 7 without any special configuration (as the hostnode has direct access to all necessary devices). | ||
− | |||
− | |||
== See also == | == See also == | ||
− | * [[NX inside | + | * [[NX inside container]] |
== External links == | == External links == | ||
− | |||
* http://forum.openvz.org/index.php?t=tree&th=235&mid=1115&&rev=&reveal= | * http://forum.openvz.org/index.php?t=tree&th=235&mid=1115&&rev=&reveal= | ||
− | * http://ait.web.psi.ch/services/linux/ | + | * http://ait.web.psi.ch/services/linux/kde-desktop-sharing.htm |
* http://ait.web.psi.ch/services/ssh/vnc-ssh.html | * http://ait.web.psi.ch/services/ssh/vnc-ssh.html | ||
* http://www.vnc.com/pipermail/vnc-list/2002-July/031831.html | * http://www.vnc.com/pipermail/vnc-list/2002-July/031831.html |