From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: Errors in man pages, here: msr(4): Content
Date: Tue, 21 Apr 2020 21:38:33 +0200 [thread overview]
Message-ID: <CAKgNAkiizD62V=Yi5Pt+3kzsgqwzzoYY+J5h2SskrHwQMd591w@mail.gmail.com> (raw)
In-Reply-To: <20200421191051.GC4951@Debian-50-lenny-64-minimal>
Hello Helge,
On Tue, 21 Apr 2020 at 21:10, Helge Kreutzmann <debian@helgefjell.de> wrote:
>
> Hello Michael,
> On Sun, Apr 19, 2020 at 10:47:38PM +0200, Michael Kerrisk (man-pages) wrote:
> > > can read proc as regular user (etch)
> > >
> > > "This file is protected so that it can be read and written only by the user "
> > > "I<root>, or members of the group I<root>."
> >
> > I need more context here to find which part of the
> > page this note refers to.
>
> This is the last paragraph before NOTES, i.e. the last one in
> DESCRIPTION.
Ooops _ I must have been looking at the wrong file.
> Having a brief look this FIXME probably is (no) longer correct, but
> the translator who noticed this 2011 is no longer active, so please
> close if it is (no longer) applicable.
Close it, I think. Certainly on my system /dev/cpu/N/msr is readable
only by root.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-04-21 19:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 6:48 Errors in man pages, here: msr(4): Content Helge Kreutzmann
2020-04-19 20:47 ` Michael Kerrisk (man-pages)
2020-04-21 19:10 ` Helge Kreutzmann
2020-04-21 19:38 ` Michael Kerrisk (man-pages) [this message]
2020-04-22 19:18 ` Helge Kreutzmann
2020-04-19 6:48 Helge Kreutzmann
2020-04-19 20:48 ` Michael Kerrisk (man-pages)
2020-04-20 8:51 ` Jakub Wilk
2020-04-20 9:02 ` 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='CAKgNAkiizD62V=Yi5Pt+3kzsgqwzzoYY+J5h2SskrHwQMd591w@mail.gmail.com' \
--to=mtk.manpages@gmail.com \
--cc=debian@helgefjell.de \
--cc=linux-man@vger.kernel.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).