Date: Sat, 3 Sep 2016 12:48:55 +0200 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= <trasz@FreeBSD.org> To: "Lundberg, Johannes" <johannes@brilliantservice.co.jp> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Weirdness in TTY & VT Message-ID: <20160903104855.GA12771@brick> In-Reply-To: <CAASDrVky8v4FWjqKYgv1mJ0-ksqVD9KWTNBNatfSVxBOBc5eyQ@mail.gmail.com> References: <CAASDrVky8v4FWjqKYgv1mJ0-ksqVD9KWTNBNatfSVxBOBc5eyQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 0902T1712, Lundberg, Johannes wrote:
> Hi
>
> I'm porting some Linux code and have some weird behavior.
>
> In this (Linux) code fstat() and minor() is used on a /dev/tty file
> descriptor to get a tty number to map to. In FreeBSD this returns a number
> around 60-70 for st_rdev which means VT_ACTIVATE ioctl call will fail
> because it only allows values 0-12.
>
> Should not this be compatible with FreeBSD? If not, what is the FreeBSD way
> to do this?
>
> Is there some implementation missing in vt?
Device numbers don't really matter in FreeBSD. To get the current
VT number, use VT_GETACTIVE ioctl. Take a look at vidcontrol(1)
source to see how it's done ("vidcontrol -i active").
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160903104855.GA12771>