From mboxrd@z Thu Jan 1 00:00:00 1970 From: bakul@bitblocks.com (Bakul Shah) Date: Mon, 06 Nov 2017 08:21:02 -0800 Subject: [TUHS] TERM for v8 In-Reply-To: Your message of "Sun, 05 Nov 2017 15:42:19 -0500." References: <7247d8f1-2100-ff26-fc33-d5e782adea7a@gmail.com> <61E89B92-FC04-43B6-9AC2-2752BC146528@ccc.com> <5da5899d-1768-7970-4316-a75c92c7cd54@gmail.com> <95C8CDF3-7290-4416-83A9-F9A23058AF3D@ccc.com> <712a3d52-7b3e-b4ac-b1c1-a65ca5a863ab@gmail.com> <20171105190037.71E88156E7D7@mail.bitblocks.com> <3c04537a-70d3-e37f-017a-0e6439c199ec@gmail.com> <20171105194334.35487156E7D7@mail.bitblocks.com> Message-ID: <20171106162117.A8F8D156E7D7@mail.bitblocks.com> On Sun, 05 Nov 2017 15:42:19 -0500 Paul Winalski wrote: Paul Winalski writes: > On 11/5/17, Bakul Shah wrote: > > > > I have no clue about v8 but at least in v7 these were > > different drivers. Looking at v7/usr/sys/dev/kl.c I don't see > > klioctl() like dzioctl() in the dz driver. So my guess is > > console ioctls return EINVAL. > > > That would seem to indicate that stty isn't checking for ioctl() > failure. Or at least it isn't displaying an error message if that > happens. Yes, v8 stty ignores all ioctl results! v8 has cons.c for the console device and it basically ignores ioctls.