LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Dax Kelson <dax@gurulabs.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Jean Delvare <khali@linux-fr.org>
Subject: Linus' laptop and Num lock status
Date: Wed, 14 Feb 2007 11:56:01 -0700	[thread overview]
Message-ID: <1171479361.3706.48.camel@mentorng.gurulabs.com> (raw)

According to the lore(1) the reason that the kernel unconditionally
turns off the num lock was so that Linus' laptop came up ready to type.

The issue is that if you force num lock on, then laptop users are messed
up since for most laptops your keyboard changes as follows:

7890 = 789*
 uiop = 456-
  jkl; = 123+
   m./ = 0./

So the only safe choice is "force off" or "Follow BIOS" (preferable).

Are there any technical or political reasons why kernel can't change
from "force off" to "Follow BIOS"?

Some distributions implement "Follow BIOS" in their bootup scripts but
the most just follow the kernel. IMHO, it would be very nice if the
"Follow BIOS" was done by the kernel so this would Just Work(tm)
everywhere in all situations (such as rescue environments where the
normal bootup scripts aren't processed).

Thanks,
Dax Kelson

(1)
http://www.redhat.com/archives/fedora-test-list/2003-September/msg00713.html


             reply	other threads:[~2007-02-14 19:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14 18:56 Dax Kelson [this message]
2007-02-14 19:12 ` Linus Torvalds
2007-02-14 19:19   ` Dax Kelson
2007-02-14 19:21   ` Jean Delvare
2007-02-14 19:32     ` Linus Torvalds
2007-02-14 21:34       ` Dax Kelson
2007-02-14 21:58         ` Jan Engelhardt
2007-02-15  0:06           ` Krzysztof Halasa
2007-02-20 13:57             ` Helge Hafting
2007-02-15  0:31           ` Alan
2007-02-18 16:19       ` Jean Delvare
2007-02-15 14:34     ` H. Peter Anvin
2007-02-18 16:04       ` Jean Delvare
2007-02-18 17:32         ` H. Peter Anvin
2007-02-18 18:06           ` Randy Dunlap
2007-02-19  0:26             ` H. Peter Anvin
2007-02-18 17:54         ` Randy Dunlap
2007-02-14 19:26   ` Arjan van de Ven
2007-02-15 14:25   ` H. Peter Anvin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1171479361.3706.48.camel@mentorng.gurulabs.com \
    --to=dax@gurulabs.com \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: Linus'\'' laptop and Num lock status' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).