From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: Errors in man pages, here: statfs(2): Typo?
Date: Mon, 20 Apr 2020 10:05:40 +0200 [thread overview]
Message-ID: <1e34d2ad-dcd8-5182-7379-0c97b076ff6a@gmail.com> (raw)
In-Reply-To: <20200419064829.GA32234@Debian-50-lenny-64-minimal>
On 4/19/20 8:48 AM, Helge Kreutzmann wrote:
> Dear manpages maintainers.
> the manpage-l10n project maintains a large number of translations of
> man pages both from a large variety of sources (including manpages) as
> well for a large variety of target languages.
>
> During their work translators notice different possible issues in the
> original (english) man pages. Sometiems this is a straightforward
> typo, sometimes a hard to read sentence, sometimes this is a convention
> not held up and sometimes we simply do not understand the original.
>
> We use several distributions as sources and update regularly (at
> least every 2 month). This means we are fairly recent (some
> distributions like archlinux also update frequently) but might miss
> the latest upstream version once a while, so the error might be
> already fixed. We apologize and ask you to close the issue immediately
> if this should be the case, but given the huge volume of projects and
> the very limited number of volunteers we are not able to double check
> each and every issue.
>
> Secondly we translators see the manpages in the neutral po format,
> i.e. converted and harmonized, but not the original source (be it man,
> groff, xml or other). So we cannot provide a true patch (where
> possible), but only an approximation which you need to translate into
> your source format.
>
> Finally the issues I'm reporting have accumulated over time and are
> not always discovered by me, so sometimes my description of the
> problem my be a bit limited - do not hesitate to ask so we can clarify
> them.
>
> I'm now reporting the errors for your project. As requested, each
> issue is sent in an unique mail for easier tracking on your side. If
> future reports should use another channel, please let me know.
>
> s/node/inode/ ?
> "struct statfs {\n"
> " __fsword_t f_type; /* Type of filesystem (see below) */\n"
> " __fsword_t f_bsize; /* Optimal transfer block size */\n"
> " fsblkcnt_t f_blocks; /* Total data blocks in filesystem */\n"
> " fsblkcnt_t f_bfree; /* Free blocks in filesystem */\n"
> " fsblkcnt_t f_bavail; /* Free blocks available to\n"
> " unprivileged user */\n"
> " fsfilcnt_t f_files; /* Total file nodes in filesystem */\n"
> " fsfilcnt_t f_ffree; /* Free file nodes in filesystem */\n"
> " fsid_t f_fsid; /* Filesystem ID */\n"
> " __fsword_t f_namelen; /* Maximum length of filenames */\n"
> " __fsword_t f_frsize; /* Fragment size (since Linux 2.6) */\n"
> " __fsword_t f_flags; /* Mount flags of filesystem\n"
> " (since Linux 2.6.36) */\n"
> " __fsword_t f_spare[xxx];\n"
> " /* Padding bytes reserved for future use */\n"
> "};\n"
>
Changed as below.
Thanks,
Michael
diff --git a/man2/statfs.2 b/man2/statfs.2
index 276ce2061..a0a64714e 100644
--- a/man2/statfs.2
+++ b/man2/statfs.2
@@ -54,8 +54,8 @@ struct statfs {
fsblkcnt_t f_bfree; /* Free blocks in filesystem */
fsblkcnt_t f_bavail; /* Free blocks available to
unprivileged user */
- fsfilcnt_t f_files; /* Total file nodes in filesystem */
- fsfilcnt_t f_ffree; /* Free file nodes in filesystem */
+ fsfilcnt_t f_files; /* Total inodes in filesystem */
+ fsfilcnt_t f_ffree; /* Free inodes in filesystem */
fsid_t f_fsid; /* Filesystem ID */
__fsword_t f_namelen; /* Maximum length of filenames */
__fsword_t f_frsize; /* Fragment size (since Linux 2.6) */
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2020-04-20 8:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 6:48 Errors in man pages, here: statfs(2): Typo? Helge Kreutzmann
2020-04-20 8:05 ` Michael Kerrisk (man-pages) [this message]
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=1e34d2ad-dcd8-5182-7379-0c97b076ff6a@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).