From: Norman Wilson <norman@oclsc.org>
To: tuhs@tuhs.org
Subject: Re: [TUHS] Cryptic Unix Commands
Date: Wed, 05 Sep 2018 11:04:41 -0400 [thread overview]
Message-ID: <1536159885.28857.for-standards-violators@oclsc.org> (raw)
Ron Natalie:
I use the numbers but I think it stems from the days when kill didn't take
the names. It's easier for me to remember -1 and -9 than to remember what
the mnemonics are.
====
Me too. And not just the kill command; the (real) shell's
trap command too.
It's all just muscle memory, not a desire to save keystrokes.
On the rare occasions when I need to send a post-modern signal
like SIGSTOP or SIGCONT, I use the name.
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? When we
taught kill about that sometime in (I think) the 9th Edition
era at Research, we allowed either form. I think it was
Doug who insisted on it, and he was right.
All this applies to shell commands, not to programs.
It is just plain wrong to code
kill(9, pid)
in C.
Norman Wilson
Toronto ON
next reply other threads:[~2018-09-05 15:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 15:04 Norman Wilson [this message]
2018-09-05 15:42 ` Chet Ramey
-- 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=1536159885.28857.for-standards-violators@oclsc.org \
--to=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).