public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: beolach@juno.com
To: pete@shinners.org
Cc: linux-newbie@vger.kernel.org
Subject: Re: boot with numlock?
Date: Sat, 1 Nov 2003 02:28:44 GMT	[thread overview]
Message-ID: <20031031.182850.28675.541204@webmail10.lax.untd.com> (raw)


Hi, Pete

For brief answer just skip to the down to the indented part.

This question is addressed in The Linux Documentation Project at
<http://www.tldp.org/> (which turns ten years old today! Hurray!).
There are two HOWTOs that pertain too your question:
The Linux Keyboard and Console HOWTO in more technical and abstract
(and less helpful, IMO) terms at:
<http://www.tldp.org/HOWTO/Keyboard-and-Console-HOWTO.html>.
The HOWTO covers a ton of info on linux keyboard & console; the
section on numlock is Section 10 "The keyboard LEDs" at:
<http://www.tldp.org/HOWTO/Keyboard-and-Console-HOWTO-10.html>.

A briefer (and better IMO) answer is in the Configuration HOWTO at
<http://www.tldp.org/HOWTO/Config-HOWTO/index.html>.  It's keyboard
section is at <http://www.tldp.org/HOWTO/Config-HOWTO/x43.html#AEN64>.
To quote this Configuration HOWTO:

    To enable NumLock on by default, add these lines to the startup
    script /etc/rc.d/rc.sysinit:
    
    for tty in /dev/tty[1-9]*; do
      setleds -D +num < $tty
    done

In this example, change the /dev/tty[1-9]* to however many consoles
you have on startup; for example my distro (Slackware) defaults to
having 6 initial consoles, so I would use: /dev/tty[1-6]*

Also note that (AFAIK) you can only set the default numlock status
for consoles that have been created; so if I boot up with the default
of 6 consoles, but later create a new virtual terminal (with openvt),
the new console would default to having numlock off.  This also means
that when you start X Windows, the numlock will most likely default to
off as well.  For X, I'm not sure how to set it to startup with numlock
on. Probably simple, but I haven't taken the time to research it.

Hope this helps,
Conway S. Smith

--------- .sig ---------
Why do programmers confuse Halloween with Christmas?
Because 31 OCT == 25 DEC.
--------- .sig ---------


-- Pete Shinners <pete@shinners.org> wrote:
>i have my bios set to boot with numlock on. i always want numlock on. 
>linux seems to default to numlock off on all the terminals. if i could 
>just fix the X terminal that would be good enough, but is there a way 
>for all the terminals to have the numlock on?


________________________________________________________________
The best thing to hit the internet in years - Juno SpeedBand!
Surf the web up to FIVE TIMES FASTER!
Only $14.95/ month - visit www.juno.com to sign up today!
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

             reply	other threads:[~2003-11-01  2:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-01  2:28 beolach [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-31 14:39 boot with numlock? Pete Shinners

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=20031031.182850.28675.541204@webmail10.lax.untd.com \
    --to=beolach@juno.com \
    --cc=linux-newbie@vger.kernel.org \
    --cc=pete@shinners.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox