From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Linux console tools development discussion <kbd@lists.altlinux.org>
Subject: Re: [kbd] New vt_mode tool for kbd?
Date: Mon, 28 Mar 2011 15:19:18 +0400 [thread overview]
Message-ID: <20110328111918.GC15694@altlinux.org> (raw)
In-Reply-To: <4D8F0463.1050207@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
On Sun, Mar 27, 2011 at 01:33:23PM +0400, Alexey Gladkov wrote:
> 27.03.2011 01:33, Dmitry V. Levin wrote:
> > Multi-value exit status is not quite script-friendly, especially for
> > values greater than 128, because exit codes greater than 128 are used
> > by the shell to indicate that a program died due to a fatal signal.
>
> I do not really like the idea of creating for each ioctl by the utility.
>
> Does anyone have any suggestions on how combine all the requests in a
> single utility?
Usage: kbdinfo [-C DEVICE] getmode [text|graphics]
kbdinfo [-C DEVICE] gkbmode [raw|xlate|mediumraw|unicode]
kbdinfo [-C DEVICE] gkbmeta [metabit|escprefix]
If only one argument is given, then just print the current mode to stdout
and exit 0 (unless ioctls returned an error).
If two arguments are given, then print nothing to stdout and exit 0 iff
the current mode matches the mode described by these two arguments.
This interface would be both script-friendly and extensible.
--
ldv
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-03-28 11:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 21:42 [kbd] New vt_mode tool for kbd? Michael Schutte
2011-03-21 22:13 ` Dmitry V. Levin
2011-03-21 22:25 ` Michael Schutte
2011-03-25 13:20 ` Alexey Gladkov
2011-03-26 17:33 ` Michael Schutte
2011-03-26 22:33 ` Dmitry V. Levin
2011-03-27 9:33 ` Alexey Gladkov
2011-03-28 10:55 ` Alexey Gladkov
2011-03-28 11:19 ` Dmitry V. Levin [this message]
2011-03-28 11:26 ` Alexey Gladkov
2011-03-28 21:07 ` Alexey Gladkov
2011-03-29 21:51 ` Dmitry V. Levin
2011-03-29 22:27 ` Alexey Gladkov
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=20110328111918.GC15694@altlinux.org \
--to=ldv@altlinux.org \
--cc=kbd@lists.altlinux.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.