X inside VE - Revision history

41.107.40.84: /* Using Xephyr */ changed comma to dot in DISPLAY value

2016-04-13T09:03:16Z

‎Using Xephyr: changed comma to dot in DISPLAY value

85.216.17.167: /* Single application */

2011-04-15T12:13:04Z

‎Single application

Jack: /* GDM */

2011-04-07T20:50:49Z

‎GDM

Kir: Reverted edits by 79.142.67.109 (Talk) to last revision by 122.116.121.30

2010-10-25T03:45:35Z

Reverted edits by 79.142.67.109 (Talk) to last revision by 122.116.121.30

79.142.67.109: comment5,

2010-10-24T20:47:21Z

comment5,

122.116.121.30: /* Errata */

2010-10-20T08:51:06Z

‎Errata

Myatus: Additional How-to external link.

2009-08-24T22:18:24Z

Additional How-to external link.

SHaggY caT: /* See also */ fix link

2008-10-04T07:52:37Z

‎See also: fix link

Kir: replaced the broken link

2008-03-11T13:49:30Z

replaced the broken link

Botinki Kira: Robot: Automated text replacement (-VE +container)

2008-03-11T13:25:09Z

Robot: Automated text replacement (-VE +container)

@@ Line 100: / Line 100: @@
 Change your display settings (don't forget to change them back after you establish a connection)
-<pre>DISPLAY=:1,0</pre>
+<pre>DISPLAY=:1.0</pre>
 Forward your application or desktop over ssh to Xephyr

@@ Line 5: / Line 5: @@
 === Single application ===
-To run an X application inside a [[container]], one need simply to connect to a container with '''ssh -X''':
+To run an X application inside a [[container]], one needs simply to connect to a container with '''ssh -X''':
 <pre>
 host# ssh -2 -c blowfish -X user@address

@@ Line 140: / Line 140: @@
 ===== GDM =====
-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.
+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. Insert '''0=inactive''' in [servers] section. Insert '''Enable=1''' in [xdmcp] section. Also, change from VCAllocation=true to VTAllocation=false and comment out the FirstVT=7 line if that lines exists. Change the access restrictions (if any) to suit your needs and then start GDM.
 === Client/Host Configuration ===

@@ Line 1: / Line 1: @@
 There are several ways to run X applications inside your [[container]].
-comment5,
+== X forwarding ==
 == VNC for X desktop ==

@@ Line 1: / Line 1: @@
 There are several ways to run X applications inside your [[container]].
-== X forwarding ==
+comment5,
 == VNC for X desktop ==

@@ Line 152: / Line 152: @@
 === 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).
 == See also ==

@@ Line 157: / Line 157: @@
 == External links ==
 * http://forum.openvz.org/index.php?t=tree&th=235&mid=1115&&rev=&reveal=
 * http://ait.web.psi.ch/services/linux/software/local/by_task/desktop_sharing/index.html

@@ Line 154: / Line 154: @@
 == See also ==
-* [[NX inside container]]
+* [[NX inside VE]]
 == External links ==

@@ Line 158: / Line 158: @@
 == External links ==
 * http://forum.openvz.org/index.php?t=tree&th=235&mid=1115&&rev=&reveal=
-* http://ait.web.psi.ch/services/linux/kde-desktop-sharing.htm
+* http://ait.web.psi.ch/services/linux/software/local/by_task/desktop_sharing/index.html
 * http://ait.web.psi.ch/services/ssh/vnc-ssh.html
 * http://www.vnc.com/pipermail/vnc-list/2002-July/031831.html

@@ Line 1: / Line 1: @@
-There are several ways to run X applications inside your [[VE]].
+There are several ways to run X applications inside your [[container]].
 == X forwarding ==
@@ Line 5: / Line 5: @@
 === Single application ===
-To run an X application inside a [[VE]], one need simply to connect to a VE with '''ssh -X''':
+To run an X application inside a [[container]], one need simply to connect to a container with '''ssh -X''':
 <pre>
 host# ssh -2 -c blowfish -X user@address
 </pre>
-After login to VE check that <code>$DISPLAY</code> variable is set and X11 forwarding is enabled:
+After login to container check that <code>$DISPLAY</code> variable is set and X11 forwarding is enabled:
 <pre>
 ve# echo $DISPLAY
@@ Line 16: / Line 16: @@
 </pre>
-In case <code>$DISPLAY</code> is not set, make sure that X forwarding is enabled in <code>sshd</code> config inside VE. In most Linux distros sshd configuration is stored in <code>/etc/ssh/sshd_config</code>. You should set parameter <code>X11Forwarding</code> to <code>yes</code>. Also VE should contain <code>xauth</code> package, thus install <code>xauth</code> if it is missing (in Debian this is part of the xbase-clients package). After that, restart your sshd daemon:
+In case <code>$DISPLAY</code> is not set, make sure that X forwarding is enabled in <code>sshd</code> config inside container. In most Linux distros sshd configuration is stored in <code>/etc/ssh/sshd_config</code>. You should set parameter <code>X11Forwarding</code> to <code>yes</code>. Also container should contain <code>xauth</code> package, thus install <code>xauth</code> if it is missing (in Debian this is part of the xbase-clients package). After that, restart your sshd daemon:
 <pre>
 ve# /etc/init.d/sshd restart
@@ Line 23: / Line 23: @@
 {{Note|Don't forget to reconnect after this}}
-Now you can run X applications from your VE:
+Now you can run X applications from your container:
 <pre>
 ve# firefox
@@ Line 47: / Line 47: @@
 == VNC for X desktop ==
-First, one need to run '''Xvnc''' server inside VE. The easiest way for this is to run
+First, one need to run '''Xvnc''' server inside container. The easiest way for this is to run
 '''vncserver''' script. This scripts starts all the required services
 and small http daemon which provides graphical web access to your desktop (via Java applet).
@@ Line 62: / Line 62: @@
 using '''vncviewer''' command:
 <pre>
-host# vncviewer <VE_IP>:1
+host# vncviewer <container_IP>:1
 </pre>
@@ Line 71: / Line 71: @@
 === Starting KDE desktop with VNC ===
 To start KDE desktop instead of default twm one replace <code>twm &</code> line with <code>startkde &</code> in user's
-<code>~/.vnc/xstartup</code> file on the VE.
+<code>~/.vnc/xstartup</code> file on the container.
 === Connecting with VNC from firewalled network ===
@@ Line 113: / Line 113: @@
 This method will give you a graphical login prompt remotely similar to VNC, but with some differences. Most notably, XDMCP is faster than VNC (due to the way each deals with screen handling) and but you CANNOT connect to existing sessions like you can with VNC. Each time you logout, your programs are closed. XDMCP is better suited in situations where you don't have a local display (or dumb terminals/clients) but want to run X11 programs
-=== VE Configuration ===
+=== container Configuration ===
 Install your desktop environment as you'd like (kde/gnome/xfce/etc) and ensure you install at least XDM. You can opt to use GDM/KDM as they also do the same job as XDM. The configuration for KDM/GDM is different than XDM's and I was only able to find one link on configuring GDM (more below).
@@ Line 126: / Line 126: @@
 (Please keep in mind the security implications by the above line. Read the comments found in the file and set it appropriately)
-To provide the possibility to run sound applications from VE, /dev/dsp device file needs to be exported in VE:
+To provide the possibility to run sound applications from container, /dev/dsp device file needs to be exported in container:
 <pre>
 vzctl set 221 --devnodes dsp:rw --save
 </pre>
-Finally, if you intend to make xdm invoking a heavy desktop like kde, it is reasonable to increase the amount of memory available for allocation inside  this VE:
+Finally, if you intend to make xdm invoking a heavy desktop like kde, it is reasonable to increase the amount of memory available for allocation inside  this container:
 <pre>
 vzctl set 221 --privvmpages 500M:600M --save
@@ Line 137: / Line 137: @@
 For light desktop like icewm this is not needed.
-Once these changes have been made, start your xdm server by the appropriate startup script (typically similar to /etc/init.d/xdm start). That concludes the XDM setup in the VE.
+Once these changes have been made, start your xdm server by the appropriate startup script (typically similar to /etc/init.d/xdm start). That concludes the XDM setup in the container.
 ===== GDM =====
@@ Line 144: / Line 144: @@
 === Client/Host Configuration ===
-On the Client/Host (whatever machine you are connecting from to the VE), you need to install ONLY a bare Xserver as per your OS instructions (use yum, emerge, apt, whatever). A desktop environment like XFCE/GNOME/KDE is entirely optional on the client, but keep in mind that it won't be used while you're connecting to the desktop on the VE.
+On the Client/Host (whatever machine you are connecting from to the container), you need to install ONLY a bare Xserver as per your OS instructions (use yum, emerge, apt, whatever). A desktop environment like XFCE/GNOME/KDE is entirely optional on the client, but keep in mind that it won't be used while you're connecting to the desktop on the container.
 To get access to the XDM server, just start an Xserver with '''X -query <remote IP> :0''' (where :0 is the local display...set to :1 if you already have an X session running, or use Xnest)
@@ Line 151: / Line 151: @@
 === Errata ===
-On a side note, as of December 2007, I was never able to successfully get an Xserver to run inside a VE 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 ==
-* [[NX inside VE]]
+* [[NX inside container]]
 == External links ==