From owner-freebsd-hackers Tue Apr 9 07:54:59 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA16496 for hackers-outgoing; Tue, 9 Apr 1996 07:54:59 -0700 (PDT) Received: from expo.x.org (expo.x.org [198.112.45.11]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA16482 for ; Tue, 9 Apr 1996 07:54:44 -0700 (PDT) Received: from exalt.x.org by expo.x.org id AA06502; Tue, 9 Apr 96 10:54:11 -0400 Received: from localhost by exalt.x.org id KAA29763; Thu, 11 Apr 1996 10:54:10 -0400 Message-Id: <199604111454.KAA29763@exalt.x.org> To: sos@FreeBSD.org Cc: hackers@freefall.FreeBSD.org Subject: Re: DVORAK keyboard drivers In-Reply-To: Your message of Tue, 09 Apr 1996 15:43:25 EST. <199604091343.PAA02475@ra.dkuug.dk> Organization: X Consortium Date: Thu, 11 Apr 1996 10:54:10 EST From: "Kaleb S. KEITHLEY" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > kbdcontrol -l us.dvorak > > Its as easy as that... > X should inherit this from the console driver too... > If kbdcontrol gave us an easy way to tell what the keymap actually is, as opposed to a bunch of raw data. I don't want to have to try to parse a keymap to tell what it is. And, as I said previously, nobody really uses the console, right? :-) X has it's own way to load specific keymaps. I'm not opposed to having the X server DTRT based on what the console driver has loaded, e.g. see the X server sources for the Xdec and Xsun servers in R6.1, but we need better support from the OS to do it. (BTW, in 2.1.0R: %kbdcontrol -d > /tmp/keymap getting keymap: Inappropriate ioctl for device Any thoughts?) -- Kaleb KEITHLEY