From owner-freebsd-current  Fri Sep  3  7:42: 5 1999
Delivered-To: freebsd-current@freebsd.org
Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33])
	by hub.freebsd.org (Postfix) with ESMTP id 1649314D7B
	for <current@freebsd.org>; Fri,  3 Sep 1999 07:42:02 -0700 (PDT)
	(envelope-from luoqi@watermarkgroup.com)
Received: (from luoqi@localhost)
	by lor.watermarkgroup.com (8.8.8/8.8.8) id KAA01499
	for current@freebsd.org; Fri, 3 Sep 1999 10:41:12 -0400 (EDT)
	(envelope-from luoqi)
Date: Fri, 3 Sep 1999 10:41:12 -0400 (EDT)
From: Luoqi Chen <luoqi@watermarkgroup.com>
Message-Id: <199909031441.KAA01499@lor.watermarkgroup.com>
To: current@freebsd.org
Subject: start xdm on a particular vty
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

There have been discussions about the xdm entry /etc/ttys does not guarantee
the X server being started on the particular vty. So I wrote a shell script
to explicitly tell xdm to start X server on a specific vty. It's been working
great. I'd like to share it with you, maybe we could include it in the base
system. Here's the script (I call it xdmstart), it's very simple,

#!/bin/sh
case $1 in
ttyv*)
	vt=vt`expr $1 : 'ttyv\(.*\)' + 1`;;
*)	vt=;;
esac
exec /usr/X11R6/bin/xdm -nodaemon -server ":0 local /usr/X11R6/bin/X :0 $vt"

and in /etc/ttys replace the xdm line with
ttyv3   "/usr/local/bin/xdmstart"      xterm   on  secure

There's one thing should be noted, the vtxx option isn't a standard X server
option, but both XFree86 and Xig support it, so majority of the people should
be covered.

-lq


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message