[gentoo-user] Setup for two graphical logins on one machine

[gentoo-user] Setup for two graphical logins on one machine

[Markus Oehme]

Hi everybody,

I've got a somewhat exotic wish: I want to have two graphical logins on my
box. Currently I'm using /etc/init.d/xdm to start slim which in turn starts
an XFce session after login. All of this happens on vt7 (reachable via
ctrl-alt-f7). Now I wish for a second graphical login on vt8.

I can get a second graphical desktop by running 'startx -- :1' in a root
shell, but this looses all advantages of management through init-scripts.

What I currently hope for is a way to tell /etc/init.d/xdm to start two
instances of slim, one on vt7 and one on vt8. Bonus points if the second
instance of slim starts a fluxbox session instead of an XFce session upon
login. Do you think this is possible?

Thanks in advance


       	  Markus

--
Aoccdrnig to a threoy, it deosn't mttaer in waht oredr the ltteers in a wrod
are, the olny iprmoatnt tihng is taht the frist and lsat ltteer are in the
rghit pclae. The rset can be a taotl mses and you can sitll raed it in msot
csaes. Tihs is bcuseae the huamn mnid deos not raed ervey lteter by istlef,
but the wrod as a wlohe. And I awlyas thought slpeling was ipmorantt.

Re: [gentoo-user] Setup for two graphical logins on one machine

[Albert Hopkins]

On Wed, 2010-11-03 at 12:53 +0100, Markus Oehme wrote:
> Hi everybody,
> 
> I've got a somewhat exotic wish: I want to have two graphical logins on my
> box. Currently I'm using /etc/init.d/xdm to start slim which in turn starts
> an XFce session after login. All of this happens on vt7 (reachable via
> ctrl-alt-f7). Now I wish for a second graphical login on vt8.

I don't know about slim, but some dm's (xdm, gdm) allow you to manage
multiple servers if/when set up that way.

> I can get a second graphical desktop by running 'startx -- :1' in a root
> shell, but this looses all advantages of management through init-scripts.

> What I currently hope for is a way to tell /etc/init.d/xdm to start two
> instances of slim, one on vt7 and one on vt8. Bonus points if the second
> instance of slim starts a fluxbox session instead of an XFce session upon
> login. Do you think this is possible?

I have no experience with slim, but this should be possible if slim
isn't bone-headed (well you'd still have to select your session from the
menu).

Re: [gentoo-user] Setup for two graphical logins on one machine

[Robin Atwood]

On Thursday 04 November 2010, Albert Hopkins wrote:
> On Wed, 2010-11-03 at 12:53 +0100, Markus Oehme wrote:
> > Hi everybody,
> > 
> > I've got a somewhat exotic wish: I want to have two graphical logins on
> > my box. Currently I'm using /etc/init.d/xdm to start slim which in turn
> > starts an XFce session after login. All of this happens on vt7
> > (reachable via ctrl-alt-f7). Now I wish for a second graphical login on
> > vt8.
> > What I currently hope for is a way to tell /etc/init.d/xdm to start two
> > instances of slim, one on vt7 and one on vt8. Bonus points if the second
> > instance of slim starts a fluxbox session instead of an XFce session upon
> > login. Do you think this is possible?

AFAIK, you must poke around in /etc/X11/ where the xserver config files are. 
XAccess seems to ring a bell! I have kdm here which does it all in one big 
kdmrc file, so I can't tell you exactly.

HTH
-Robin
-- 
----------------------------------------------------------------------
Robin Atwood.

"Ship me somewheres east of Suez, where the best is like the worst,
 Where there ain't no Ten Commandments an' a man can raise a thirst"
         from "Mandalay" by Rudyard Kipling
----------------------------------------------------------------------

[solved] Re: [gentoo-user] Setup for two graphical logins on one machine

[Markus Oehme]

[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]

Hi everybody,

I managed to get it running as I wished. The only thing, that I couldn't
solve in a nice way was using fluxbox instead of Xfce upon login in xdm, but
a little hack did the trick.

I left my setup as described and added an init-script /etc/init.d/xdm2 which
is mostly copy and paste from /etc/init.d/xdm trimmed down to what I
actually need. It simply starts xdm, which does the Right Things(tm) after
configuration. I edited /etc/X11/xdm/Xservers to account for the allready
running X. Then I hacked /etc/X11/xdm/xdm-config to point to fluxbox in a
hard-coded way.

That's it. Works fine :)


       	   Markus


--
Aoccdrnig to a threoy, it deosn't mttaer in waht oredr the ltteers in a wrod
are, the olny iprmoatnt tihng is taht the frist and lsat ltteer are in the
rghit pclae. The rset can be a taotl mses and you can sitll raed it in msot
csaes. Tihs is bcuseae the huamn mnid deos not raed ervey lteter by istlef,
but the wrod as a wlohe. And I awlyas thought slpeling was ipmorantt.


[-- Attachment #2: xdm2 --]
[-- Type: application/octet-stream, Size: 1463 bytes --]

#!/sbin/runscript
# Copyright 1999-2010 Gentoo Foundation
# Distributed under the terms of the GNU General Public License, v2
# $Header: /var/cvsroot/gentoo-x86/x11-base/xorg-server/files/xdm.initd-3,v 1.1 2010/09/28 12:43:19 scarabeus Exp $

depend() {
	need localmount xdm-setup

	# this should start as early as possible
	# we can't do 'before *' as that breaks it
	# (#139824) Start after ypbind and autofs for network authentication
	# (#145219 #180163) Could use lirc mouse as input device
	# (#70689 comment #92) Start after consolefont to avoid display corruption
	# (#291269) Start after quota, since some dm need readable home
	after bootmisc consolefont modules netmount
	after readahead-list ypbind autofs openvpn gpm lircmd
	after quota
	before alsasound

	# Start before X
	use consolekit xfs

	# don't mess up terminals
	after xdm
}

start() {
	ebegin "Setting up XDM"
	# sleep some time after slim startup otherwise the second X server crashes
	sleep 5
        start-stop-daemon --start --exec /usr/bin/xdm --pidfile /var/run/xdm.pid || eerror "ERROR: could not start the Display Manager"
	eend 0
}

stop() {

       	[ -z "/usr/bin/xdm" ] && return 0

	ebegin "Stopping XDM"

	if start-stop-daemon --quiet --test --stop --exec "/usr/bin/xdm"; then
		start-stop-daemon --stop --exec "/usr/bin/xdm" --retry TERM/5/TERM/5 \
			--pidfile /var/run/xdm.pid
		retval=${?}
	fi

	eend ${retval} "Error stopping XDM"
	return ${retval}
}

# vim: set ts=4 :

[-- Attachment #3: Xservers --]
[-- Type: application/octet-stream, Size: 487 bytes --]

# $Xorg: Xserv.ws.cpp,v 1.3 2000/08/17 19:54:17 cpqbld Exp $
#
# Xservers file, workstation prototype
#
# This file should contain an entry to start the server on the
# local display; if you have more than one display (not screen),
# you can add entries to the list (one per line).  If you also
# have some X terminals connected which do not support XDMCP,
# you can add them here as well.  Each X terminal line should
# look like:
#	XTerminalName:0 foreign
#
:1 local /usr/bin/X :1 vt8

[-- Attachment #4: xdm-config --]
[-- Type: application/octet-stream, Size: 1374 bytes --]

! $Xorg: xdm-conf.cpp,v 1.3 2000/08/17 19:54:17 cpqbld Exp $
! $XdotOrg: $    
!
!
!
!
! $XFree86: xc/programs/xdm/config/xdm-conf.cpp,v 1.10 2002/11/30 19:11:32 herrb Exp $
!






DisplayManager.errorLogFile:	/var/log/xdm.log
DisplayManager.pidFile:		/var/run/xdm.pid
DisplayManager.keyFile:		/etc/X11/xdm/xdm-keys
DisplayManager.servers:		/etc/X11/xdm/Xservers
DisplayManager.accessFile:	/etc/X11/xdm/Xaccess
DisplayManager*resources:	/etc/X11/xdm/Xresources
DisplayManager.willing:		/usr/lib64/X11/xdm/Xwilling
! All displays should use authorization, but we cannot be sure
! X terminals may not be configured that way, so they will require
! individual resource settings.
DisplayManager*authorize:	true
!
DisplayManager*chooser:		/usr/lib64/X11/xdm/chooser
DisplayManager*startup:		/usr/lib64/X11/xdm/Xstartup
DisplayManager*session:		/etc/X11/Sessions/fluxbox
DisplayManager*reset:		/usr/lib64/X11/xdm/Xreset
DisplayManager*authComplain:	true
! The following three resources set up display :0 as the console.
DisplayManager._0.setup:	/usr/lib64/X11/xdm/Xsetup_0
DisplayManager._0.startup:	/usr/lib64/X11/xdm/GiveConsole
DisplayManager._0.reset:	/usr/lib64/X11/xdm/TakeConsole

DisplayManager*loginmoveInterval:	10

! SECURITY: do not listen for XDMCP or Chooser requests
! Comment out this line if you want to manage X terminals with xdm
DisplayManager.requestPort:	0