All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Default keyboard LEDs
Date: Mon, 14 Jan 2008 10:24:28 +0000	[thread overview]
Message-ID: <20080114102428.GA4298@implementation.uk.xensource.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0801140238260.10906@fbirervta.pbzchgretzou.qr>

Jan Engelhardt, le Mon 14 Jan 2008 02:40:08 +0100, a écrit :
> 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`)

But it is a burden (you forgot '&' btw ;) ). Also, openvt properly sets
the controlling tty, can run a login shell, etc...

Anyway, be it openvt or bash, the LED issue exists :)

Samuel
-
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Default keyboard LEDs
Date: Mon, 14 Jan 2008 10:24:28 +0000	[thread overview]
Message-ID: <20080114102428.GA4298@implementation.uk.xensource.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0801140238260.10906@fbirervta.pbzchgretzou.qr>

Jan Engelhardt, le Mon 14 Jan 2008 02:40:08 +0100, a écrit :
> 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`)

But it is a burden (you forgot '&' btw ;) ). Also, openvt properly sets
the controlling tty, can run a login shell, etc...

Anyway, be it openvt or bash, the LED issue exists :)

Samuel

  reply	other threads:[~2008-01-14 10:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-14  0:52 [PATCH] Default keyboard LEDs Samuel Thibault
2008-01-14  1:40 ` Jan Engelhardt
2008-01-14 10:24   ` Samuel Thibault [this message]
2008-01-14 10:24     ` Samuel Thibault
2008-01-14  3:50 ` H. Peter Anvin
2008-01-14 10:27   ` Samuel Thibault
2008-01-14 10:27     ` Samuel Thibault

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=20080114102428.GA4298@implementation.uk.xensource.com \
    --to=samuel.thibault@ens-lyon.org \
    --cc=jengelh@computergmbh.de \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.