From owner-freebsd-current Mon Feb 19 10:23:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA13941 for current-outgoing; Mon, 19 Feb 1996 10:23:53 -0800 (PST) Received: from irz201.inf.tu-dresden.de (irz201.inf.tu-dresden.de [141.76.1.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA13929 for ; Mon, 19 Feb 1996 10:23:35 -0800 (PST) Received: from sax.sax.de by irz201.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id TAA22668; Mon, 19 Feb 1996 19:22:29 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id TAA17148; Mon, 19 Feb 1996 19:22:28 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id TAA12654; Mon, 19 Feb 1996 19:10:04 +0100 (MET) From: J Wunsch Message-Id: <199602191810.TAA12654@uriah.heep.sax.de> Subject: Re: Keyboard lockout on 2.x.x To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 19 Feb 1996 19:10:03 +0100 (MET) Cc: KentH@HNS.St-Louis.Mo.US In-Reply-To: <199602191157.FAA00984@gwydion.hns.st-louis.mo.us> from "Kent Hamilton" at Feb 19, 96 05:57:09 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk As Kent Hamilton wrote: > I remembered someone saying it had to do with the LED's, I have > re-set the machines to not turn them on at boot and I almost never > use a caps/num lock anyway. What else will toggle the LED states? > Scroll lock which I never use... anything else? It doesn't matter whether LEDs would really be toggled. The command is always sent to the keyboard on a VT switch, even if the update will yield the same LED state as previously. Hence the line conflict will always happen. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)