> On 4 Mar 1998, Wolfgang Rupprecht wrote:
> : haszlaki@uaccess.net writes:
> : > 	Boot NetBSD with a recent /etc/rc, xdm enabled, and a couple things
> port-i386 under "pcvt", right?
yep.

> The simplest fix for this is not to use hackery after rc is finished; it is
> to specify explicitly which tty you want the X server to show up on.  Using
> the "standard" NetBSD X distribution based on XFree86, this is simple.

	I wasn't really of that as a fix since what I am considering
broken is the action where xdm automatically find the first non-used tty
and uses it.  Having to hardcode a tty in Xservers obviously is not
automatic.  

> : When I run sshd from /etc/rc, xdm which is started a bit later can't
> : bind to /dev/ttyv0 and instead grabs /dev/ttyv1 with the obvious
> : results.  X and the getty fight for keboard events and eventually X
> : loses control of the keyboard.  When I turned off ssh, then X gets
> : ttyv0 and all is happy.
> Your best solution is to have getty on ttyv0, not ttyv1, and run X on ttyv1. 
> You should then have no problems with either sshd or X-vs-getty.   Use the
> fix I describe above for this PR to do that.
	uh.. what?  I'm confused.  Why does sshd grab ttyv0?  How does X end
up on ttyv0?  On my machine it always skips v0 even if gettys aren't running
yet.  (hmm.. init probably has v0 for output from /etc/rc (?))

eric
haszlaki@uaccess.net