From: Chet Ramey <chet.ramey@case.edu>
To: Norman Wilson <norman@oclsc.org>, tuhs@tuhs.org
Subject: Re: [TUHS] Cryptic Unix Commands
Date: Wed, 5 Sep 2018 11:42:09 -0400 [thread overview]
Message-ID: <8a4c50b5-bd1f-3778-5166-a0a886a59e31@case.edu> (raw)
In-Reply-To: <1536159885.28857.for-standards-violators@oclsc.org>
On 9/5/18 11:04 AM, Norman Wilson wrote:
> As an aside, why do modern kill and sh accept only the
> abbreviated form of the signal name, not the full name;
> e.g. kill -STOP is OK, kill -SIGSTOP an error?
It's the standard:
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/kill.html#tag_20_64
"Historical versions of kill have not written the SIG prefix for the -l
option and have not recognized the SIG prefix on signal_names."
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_28
"Implementations may also accept the names with the SIG prefix; no known
historical shell does so."
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
next prev parent reply other threads:[~2018-09-05 15:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 15:04 Norman Wilson
2018-09-05 15:42 ` Chet Ramey [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-05 15:44 Noel Chiappa
2018-09-05 16:12 ` John P. Linderman
2018-09-05 16:45 ` Kurt H Maier
2018-08-24 16:06 [TUHS] Research UNIX on the AT&T 3B2? Clem Cole
2018-08-27 15:54 ` Mary Ann Horton
2018-08-27 17:33 ` Clem Cole
2018-08-28 0:24 ` Dave Horsfall
2018-08-28 0:30 ` Larry McVoy
2018-08-28 6:01 ` arnold
2018-08-28 22:33 ` Dave Horsfall
2018-08-29 0:36 ` Harald Arnesen
2018-08-29 1:06 ` Dave Horsfall
2018-08-29 3:23 ` Theodore Y. Ts'o
2018-08-29 4:36 ` [TUHS] Cryptic Unix Commands Warren Toomey
2018-08-29 16:13 ` Jeremy C. Reed
2018-08-29 22:03 ` Dave Horsfall
2018-08-29 22:09 ` Grant Taylor via TUHS
2018-08-29 22:21 ` William Pechter
2018-08-29 23:04 ` Grant Taylor via TUHS
2018-08-29 23:38 ` Larry McVoy
2018-08-30 3:59 ` William Pechter
2018-08-29 22:31 ` Dan Mick
2018-08-29 23:00 ` Grant Taylor via TUHS
2018-08-30 8:28 ` Dave Horsfall
2018-08-30 11:06 ` ron
2018-08-30 11:35 ` John P. Linderman
2018-08-30 13:24 ` Clem Cole
2018-08-30 14:31 ` William Pechter
2018-08-30 15:01 ` Clem Cole
2018-08-30 15:22 ` Warner Losh
2018-08-30 16:11 ` William Pechter
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=8a4c50b5-bd1f-3778-5166-a0a886a59e31@case.edu \
--to=chet.ramey@case.edu \
--cc=norman@oclsc.org \
--cc=tuhs@tuhs.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 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).