From owner-freebsd-hackers Wed Apr 10 05:50:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA01713 for hackers-outgoing; Wed, 10 Apr 1996 05:50:34 -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 FAA01703 for ; Wed, 10 Apr 1996 05:50:28 -0700 (PDT) Received: from exalt.x.org by expo.x.org id AA21676; Wed, 10 Apr 96 08:49:55 -0400 Received: from localhost by exalt.x.org id IAA01879; Wed, 10 Apr 1996 08:49:46 -0400 Message-Id: <199604101249.IAA01879@exalt.x.org> To: J Wunsch Cc: hackers@freefall.FreeBSD.org Subject: Re: DVORAK keyboard drivers In-Reply-To: Your message of Wed, 10 Apr 1996 13:36:53 EST. <199604101136.NAA13190@uriah.heep.sax.de> Organization: X Consortium Date: Wed, 10 Apr 1996 08:49:45 EST From: "Kaleb S. KEITHLEY" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > As Kaleb S. KEITHLEY wrote: > > > > 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. > > This used to work before the xkb code went in. The point being? > (I admit that the > *way* how it worked was quite painful, but the initial mapping was > there in place.) If you don't want the features of XKB, run the server with -xkb or add XkbDisable to your XF86Config. Really, how tough is it to edit your XF86Config file? Yeah, it'd be nice if you didn't have to do it two places, but it doesn't take a PhD to do it either, so kwicherbitchen and edit your XF86Config file to make XKB load the keymap you want. If you want XKB in XFree86 to automatically work better on FreeBSD then I need some better support at the OS level. -- Kaleb "Grumpy" KEITHLEY