linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonny Grant <jg@jguk.org>
To: Michael Kerrisk <mtk.manpages@gmail.com>,
	linux-man <linux-man@vger.kernel.org>
Subject: core(5)
Date: Sat, 6 Jun 2020 14:18:12 +0100	[thread overview]
Message-ID: <9000a831-9a0f-0577-5755-95b301218383@jguk.org> (raw)

Hello

Some feedback on this page
https://man7.org/linux/man-pages/man5/core.5.html

1) "disk file" sounds rather old fashioned, usually would just say "file", on this page, removing the word "disk"

"The default action of certain signals is to cause a process to
terminate and produce a /core dump file/, a disk file containing an"


2) We wouldn't regularly say "nonwritable" in English, "not writeable" is better English


3) Could i ask to clarify my understanding. For this "The binary being executed by the process does not have read
           permission enabled."
-- is this when the binary permissions are changed after it starts running?
I thought a core file was just a dump from RAM, does it really even need to open the ELF file again?


4) I noticed %P always gave me P1200 even after a reboot I recall, I had expected it be '1', do you see similar?

Cheers, Jonny

             reply	other threads:[~2020-06-06 13:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-06 13:18 Jonny Grant [this message]
2020-06-06 14:50 ` core(5) Jakub Wilk
2020-06-06 15:45   ` core(5) Jonny Grant
2020-06-06 18:32     ` core(5) Jakub Wilk
2020-06-06 19:39       ` core(5) Michael Kerrisk (man-pages)
2020-06-06 21:16         ` core(5) Jonny Grant
2020-06-08 16:18           ` core(5) Michael Kerrisk (man-pages)
2020-06-08 16:06 ` core(5) Michael Kerrisk (man-pages)

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=9000a831-9a0f-0577-5755-95b301218383@jguk.org \
    --to=jg@jguk.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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).