From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Kai Mäkisara (Kolumbus)" <kai.makisara@kolumbus.fi>
Cc: Helge Kreutzmann <debian@helgefjell.de>,
linux-man <linux-man@vger.kernel.org>
Subject: Re: Errors in man pages, here: st(4): Content
Date: Mon, 20 Apr 2020 20:29:32 +0200 [thread overview]
Message-ID: <CAKgNAkgrAUWJyjtv8Q=Pwwa_=QThTaQGz4v_W46+5gD7QEHEJA@mail.gmail.com> (raw)
In-Reply-To: <4A645675-6A27-4CC9-B8A8-EB7644DEC710@kolumbus.fi>
Hello Kai,
On Mon, 20 Apr 2020 at 17:51, "Kai Mäkisara (Kolumbus)"
<kai.makisara@kolumbus.fi> wrote:
>
>
>
> > On 20. Apr 2020, at 11.13, Michael Kerrisk (man-pages) <mtk.manpages@gmail.com> wrote:
> >
> > [CC += Kai]
> >
> > (Kai, I got a pile of queries from a downstream translation project)
> >
> > On 4/19/20 8:48 AM, Helge Kreutzmann wrote:
> >> Dear manpages maintainers.
> >>
> ...
> >> We cannot understand the last sentence. What is "forward spacing"?
> >>
> >> "This option causes the B<MTEOM> operation to be sent directly to the drive, "
> >> "potentially speeding up the operation but causing the driver to lose track "
> >> "of the current file number normally returned by the B<MTIOCGET> request. If "
> >> "B<MT_ST_FAST_EOM> is false, the driver will respond to an B<MTEOM> request "
> >> "by forward spacing over files."
> >
> > Perhaps Kai can help. I do not have a good explanation.
> >
> Spacing in tape terminology means going to the next file (or record or set mark).
> The drives usually support a command to go to the end of the tape. The
> drawback is that no information is obtained about the number of files skipped.
> If the driver spaces forward over files one by one, it can count how many
> files have been skipped.
>
> This is the technical description. But the text also says what is the consequence
> for a user that does not care about technology. Spacing is mentions also
> earlier in the text.
So, no text changes needed here, right?
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-20 18:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 6:48 Errors in man pages, here: st(4): Content Helge Kreutzmann
2020-04-20 8:13 ` Michael Kerrisk (man-pages)
2020-04-20 15:51 ` "Kai Mäkisara (Kolumbus)"
2020-04-20 18:29 ` Michael Kerrisk (man-pages) [this message]
2020-04-20 18:51 ` "Kai Mäkisara (Kolumbus)"
2020-04-25 10:15 ` Helge Kreutzmann
2020-04-19 6:48 Helge Kreutzmann
2020-04-20 8:11 ` Michael Kerrisk (man-pages)
2020-04-20 15:42 ` "Kai Mäkisara (Kolumbus)"
2020-04-20 18:28 ` 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='CAKgNAkgrAUWJyjtv8Q=Pwwa_=QThTaQGz4v_W46+5gD7QEHEJA@mail.gmail.com' \
--to=mtk.manpages@gmail.com \
--cc=debian@helgefjell.de \
--cc=kai.makisara@kolumbus.fi \
--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).