Re: start xdm on a particular vty
Do you know the appropriate channel to contact the XFree86 folks? In the mean while, I can take Sheldon's advice, submit it to our XFree86 port. By the way, I've just thought of something you should consider. I think there's still a problem with xdm, where trying to change vty while it's starting up can lose you access to all your vtys. This isn't a problem with xdm, but with syscons. There were some patches floating around that fixed this is a really kludgey way posted or send-pr'd a while back that supposedly fixed this, but no-one followed up on it (including myself...) Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: start xdm on a particular vty
On Fri, 03 Sep 1999 14:03:11 -0400, Luoqi Chen wrote: Do you know the appropriate channel to contact the XFree86 folks? In the mean while, I can take Sheldon's advice, submit it to our XFree86 port. By the way, I've just thought of something you should consider. I think there's still a problem with xdm, where trying to change vty while it's starting up can lose you access to all your vtys. This is a problem if xdm starts up unexpectedly. This is why I'm in favour of it being part of XFree86 instead of FreeBSD. But even more important, it should only be installed if the person running the install is okay with it. For the port, that means asking another question. However, it's a little more tricky for the package and you'll probably have to warn that it has been installed, rather than ask whether it's okay to install. This is, of course, idealism. If the script becomes a part of life, people will learn. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
start xdm on a particular vty
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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: start xdm on a particular vty
On Fri, 03 Sep 1999 10:41:12 -0400, Luoqi Chen wrote: 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. I think it'd make a lot more sense if it were part of the XFree86 port. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: start xdm on a particular vty
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. I *like* it. I think you should share it with the XFree86 folks, and I think this would be great to have in the base installation (after proper testing of course...). Do you know the appropriate channel to contact the XFree86 folks? In the mean while, I can take Sheldon's advice, submit it to our XFree86 port. However, does this work with non-XFree86 X servers? (Or, maybe you can't test that...) I've only tested it with XFree86. Xig's document indicates it also supports the vtxx option (but I am unable to test it). I don't know anything about servers from other vendors. Nate -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: start xdm on a particular vty
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. I *like* it. I think you should share it with the XFree86 folks, and I think this would be great to have in the base installation (after proper testing of course...). Do you know the appropriate channel to contact the XFree86 folks? Try [EMAIL PROTECTED], who is supposedly the FreeBSD contact for XFree86. However, does this work with non-XFree86 X servers? (Or, maybe you can't test that...) I've only tested it with XFree86. Xig's document indicates it also supports the vtxx option (but I am unable to test it). I don't know anything about servers from other vendors. Great. I'll see if I can try it out at home on my XIG server... Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: start xdm on a particular vty
Luoqi Chen scribbled this message on Sep 3:
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
eval i=\$$#
case $i
ttyv*)
vt=vt`expr $1 : 'ttyv\(.*\)' + 1`;;
*)vt=;;
esac
exec /usr/X11R6/bin/xdm -nodaemon -server ":0 local /usr/X11R6/bin/X :0 $vt"
then you have a section like:
i=1
st=""
while [ $i -lt $# ]; do
st="$st"' "$'${i}'"'
i=$(($i + 1))
done
eval exec /usr/X11R6/bin/xdm -nodaemon -server \":0 local /usr/X11R6/bin/X $st :0
\$vt\"
that way you can provide -query hostname or another argument to the
Xserver..
I haven't tested that the eval exec line works properly, but I do know
that the rest of the script works fine though... :)
--
John-Mark Gurney Voice: +1 541 684 8449
Cu Networking P.O. Box 5693, 97405
"The soul contains in itself the event that shall presently befall it.
The event is only the actualizing of its thought." -- Ralph Waldo Emerson
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
