linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pádraig Brady" <P@draigBrady.com>
To: Martin Tournoij <martin@arp242.net>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
	Austin S Hemmelgarn <ahferroin7@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] The SIGINFO signal from BSD
Date: Thu, 06 Nov 2014 14:19:25 +0100	[thread overview]
Message-ID: <545B755D.4090900@draigBrady.com> (raw)
In-Reply-To: <1415225591.3444747.187568145.134CEE91@webmail.messagingengine.com>

On 11/05/2014 11:13 PM, Martin Tournoij wrote:
> On Wed, Nov 5, 2014, at 20:31, Austin S Hemmelgarn wrote:
>> The people to talk to about that for the core 
>> utilities on Linux would be the maintainers of the GNU coreutils, or 
>> whatever your distribution might use in their place (I think it's very 
>> unlikely that busybox or toybox would implement it however).
> 
> Well, if the kernel doesn't provide the feature, then we can be sure it
> will never be implemented :-)
> I thought this was a good place to start asking,, and even if GNU
> coreutils opt to not implement this for whatever reasons, other
> applications still can (mine will!)

GNU coreutils dd will already support SIGINFO if available
(and if dd is recompiled with appropriate headers).
dd currently emulates that using SIGUSR1 though as you say
that's awkward to support robustly, and there has been
a recent GNU coreutils change in relation to that:
http://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commit;h=27d2c738

I like the idea of making SIGINFO generally available
and GNU coreutils at least would add extra handling
to cp etc. if that was the case.

thanks,
Pádraig.

  reply	other threads:[~2014-11-06 13:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-05 15:17 [RFC] The SIGINFO signal from BSD 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 [this message]
2014-11-10 14:22     ` One Thousand Gnomes
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=545B755D.4090900@draigBrady.com \
    --to=p@draigbrady.com \
    --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;
as well as URLs for NNTP newsgroup(s).