[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0801140238260.10906@fbirervta.pbzchgretzou.qr>
Date: Mon, 14 Jan 2008 02:40:08 +0100 (CET)
From: Jan Engelhardt <jengelh@...putergmbh.de>
To: Samuel Thibault <samuel.thibault@...-lyon.org>
cc: linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Default keyboard LEDs
On Jan 14 2008 00:52, Samuel Thibault wrote:
>
>In many cases, one prefers to have e.g. the NumLock on by default. In
>many cases, one doesn't want to have it by default, e.g. on laptops.
>
>Distributions actually have a very hard time trying to set this
>correctly after the kernel boot, and that doesn't work for new consoles
>that are created via the openvt(1) command anyway. This hence adds a
>keyboard.default_leds boot parameter that permits to configure the
>default keyboard LEDs.
Apart from openvt being able to find the first unused tty,
what is openvt good for? (Read: I could just as well run
`bash </dev/tty8 >/dev/tty8 2>/dev/tty8`)
--
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/
Powered by blists - more mailing lists