linux-kernel - Re: Linus' laptop and Num lock status

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0702141104210.3604@woody.linux-foundation.org>
Date:	Wed, 14 Feb 2007 11:12:23 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Dax Kelson <dax@...ulabs.com>
cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Jean Delvare <khali@...ux-fr.org>
Subject: Re: Linus' laptop and Num lock status



On Wed, 14 Feb 2007, Dax Kelson wrote:
> 
> Are there any technical or political reasons why kernel can't change
> from "force off" to "Follow BIOS"?

How would you query it? I'm not even 100% sure that you can on all 
keyboards. We never query the leds, we always set them. I think. I don't 
know of any AT kbd command to read the led state out of the keyboard.

		Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/