From owner-freebsd-questions@FreeBSD.ORG Sun Dec 27 08:19:02 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB69F1065672; Sun, 27 Dec 2009 08:19:02 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26]) by mx1.freebsd.org (Postfix) with ESMTP id 3763F8FC0C; Sun, 27 Dec 2009 08:19:01 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 9so1186169eyd.3 for ; Sun, 27 Dec 2009 00:18:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.86.132 with SMTP id w4mr211194wee.87.1261901932035; Sun, 27 Dec 2009 00:18:52 -0800 (PST) In-Reply-To: <20091227080345.GA30917@thought.org> References: <20091227080345.GA30917@thought.org> Date: Sun, 27 Dec 2009 03:18:51 -0500 Message-ID: From: "b. f." To: Gary Kline Content-Type: text/plain; charset=ISO-8859-1 Cc: ed@freebsd.org, freebsd-questions@freebsd.org Subject: Re: clicky driver X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Dec 2009 08:19:02 -0000 On 12/27/09, Gary Kline wrote: > On Sun, Dec 27, 2009 at 02:11:55AM -0500, b. f. wrote: > A BEL-per-key drove me beyond the limits back in '99; that isn't > the answer, but to key a truncated bell, a click, at something well > below middle-C: yes, this kind of thing is what I'm thinking of. Remember, you can control the pitch and duration of the bell, and this can change the character of the sound substantially. Try it and see. > What is ed's full email ed[at] where.org, please. Guess: FreeB _ _.org. :) (He's cc'ed.) > > If he'll give me the clues, I'll share in the hacking. It is time > to get this feature builtin to the kernel. Off by default, and on > at some user-tuneable values. If you are talking about doing this by making the keymaps more flexible, it is easily user-configurable, though perhaps not in an on/off fashion. ed@ was writing a new console driver for other reasons, among them unicode support, and I don't know if he planned to tinker with the keyboard-handling code beyond what would be required for a interface to a different console driver, but he may be willing to help. b.