Index | Thread | Search

From:
"Theo de Raadt" <deraadt@openbsd.org>
Subject:
Re: sparc64: X and getty sharing raw keyboard input
To:
Ted Bullock <tbullock@comlore.com>
Cc:
Mark Kettenis <mark.kettenis@xs4all.nl>, tech@openbsd.org
Date:
Tue, 13 Oct 2026 16:58:37 -0600

Download raw body.

Thread
Ted Bullock <tbullock@comlore.com> wrote:

> I'm using the first arrangement you describe. Only console is enabled in
> /etc/ttys, and there's only one getty running. The individual console
> devices are disabled, which matches the current sparc64 defaults. My
> console terminal type is rcons-color rather than sun.
> 
> The competing readers were X and that one getty, rather than two gettys.
> With the default standard keyboard protocol, X reads /dev/ttyD0 and getty
> reads /dev/console, which forwards to the same terminal input queue.
> 
> Does the restriction also cover X holding the underlying terminal open
> with this arrangement? I'm trying to understand whether there's another
> setting needed beyond the current sparc64 defaults. Selecting wskbd for
> X locally separates the input and addresses the problem on this machine.

You may need to step back to understand this.

On amd64, the "console" is a redirection to some special device.

What is it on sparc64?  Oh. It is not a redirection.  It *IS* a device.