From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Austin S Hemmelgarn <ahferroin7@gmail.com>,
Martin Tournoij <martin@arp242.net>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] The SIGINFO signal from BSD
Date: Mon, 10 Nov 2014 14:22:00 +0000 [thread overview]
Message-ID: <20141110142200.676b5d04@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <20141105201404.GH27083@thunk.org>
> wouldn't be accepted. (BTW, if you're going to do this, note that ^T
> could be remapped to any control character via stty; so to do this we
> would need to define an extra index in c_cc[] array in the struct
> termios.)
We have 19 entries in the array and no platforms that byte pack so that
would actually be doable I think.
I'm really dubious about its value in the Linux world. You could do far
better teaching the GUI desktop to walk the process tree of clients and
dump the window owners process subtrees in a nice pop up window.
PS: Austin - SIGPWR was used on the System 5 boxes I used to indicate
power had been *restored* not lost. The primary usage was in curses and
termios using apps so that when the power came back on they would redraw
the screens on all the terminals.
You have to think back to a world of a generator/battery backed servers
and non battery backed terminals for that to make sense.
Alan
next prev parent reply other threads:[~2014-11-10 14:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 15:17 Martin Tournoij
2014-11-05 19:31 ` Austin S Hemmelgarn
2014-11-05 20:14 ` Theodore Ts'o
2014-11-05 20:30 ` Austin S Hemmelgarn
2014-11-05 22:13 ` Martin Tournoij
2014-11-06 13:19 ` Pádraig Brady
2014-11-10 14:22 ` One Thousand Gnomes [this message]
2014-11-10 14:34 ` Martin Tournoij
2014-11-10 16:16 ` Austin S Hemmelgarn
2014-11-23 9:48 ` Pavel Machek
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=20141110142200.676b5d04@alan.etchedpixels.co.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=ahferroin7@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@arp242.net \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®