From: usotsuki@buric.co (Steve Nickolas)
Subject: [TUHS] Origin of 'kill -9'?
Date: Tue, 14 Nov 2017 15:11:57 -0500 (EST) [thread overview]
Message-ID: <alpine.BSF.2.02.1711141510250.58112@frieza.hoshinet.org> (raw)
In-Reply-To: <20171114200751.3536621358@orac.inputplus.co.uk>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 504 bytes --]
On Tue, 14 Nov 2017, Ralph Corderoy wrote:
> Hi Dan,
>
>> Is the reason that SIGKILL has the numeric value 9
>
> If you look at signals 1 to 8 they could all be caught, etc.
> 9 was added so to thwart this and just took the next number AFAIK.
> Doesn't 9 have tie-ins to "death" in Japan? ISTR some marketing
> avoiding it in version numbers.
I think 9 has ties to "pain", but the number that has connection to
"death" in Japanese is 4 (四 shi, "four", which sounds like 死 shi,
"death").
-嘘.
next prev parent reply other threads:[~2017-11-14 20:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 19:03 Dan Cross
2017-11-14 20:07 ` Ralph Corderoy
2017-11-14 20:11 ` Steve Nickolas [this message]
2017-11-14 22:35 ` Ralph Corderoy
2017-11-15 21:52 ` Don Hopkins
2017-11-15 22:51 ` Steffen Nurpmeso
2017-11-15 23:01 ` Steve Simon
2017-11-16 6:00 ` Lars Brinkhoff
2017-11-16 6:03 ` Warner Losh
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=alpine.BSF.2.02.1711141510250.58112@frieza.hoshinet.org \
--to=usotsuki@buric.co \
/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).