From: Karel Zak <kzak@redhat.com>
To: Sami Kerola <kerolasa@iki.fi>, util-linux@vger.kernel.org
Subject: Re: [PATCH 3/4] docs: improve setarch(8) manual page
Date: Mon, 11 Dec 2017 14:46:53 +0100 [thread overview]
Message-ID: <20171211134653.wthtrktw373udxdw@ws.net.home> (raw)
In-Reply-To: <20171209012937.GA27446@altlinux.org>
On Sat, Dec 09, 2017 at 04:29:37AM +0300, Dmitry V. Levin wrote:
> On Mon, Dec 04, 2017 at 01:20:01PM +0000, Sami Kerola wrote:
> > On 4 December 2017 at 12:04, Karel Zak wrote:
> > > On Sun, Dec 03, 2017 at 12:51:16PM +0000, Sami Kerola wrote:
> [...]
> > >> \fB\-\-4gb\fR
> > >> -Ignored (for backward compatibility only).
> > >> +Ignored for backward compatibility only.
> > >
> > > Dmitry is right, the old version is better.
> >
> > How about text:
> >
> > This option is no-op compatibility with an old Debian setarch
> > implementation. Please do not use.
>
> Let's add a description that is informative but without giving advice.
Yes, and without any distro name...
> For example,
>
> "This option has no effect. It is retained for backward compatibility only,
> and may be removed in future releases."
+1
> > How about this:
> >
> > -- snip
> > This makes
> > .BR select (2),
> > .BR pselect (2),
> > and
> > .BR ppoll (2)
> > system calls preserve the timeout value instead of storing the unslept time
>
> I'm not sure about "unslept time" phrase. Wouldn't a more formal
> description be better, .e.g.
>
> This makes
> ...
> system calls preserve the timeout value instead of modifying it to reflect
> the amount of time not slept when interrupted by a signal handler.
> ...
+1
>
> > when interrupted by a signal handler. Use when
> > .I program
> > depends on this behavior. For more details see the timeout description from
>
> s/from/in/
>
> > .BR select (2)
> > manual page. Turns on STICKY_TIMEOUTS.
> > -- snip
>
> On the whole, this looks much better.
>
> > My remote git has the latest.
> >
> > https://github.com/kerolasa/lelux-utiliteetit/blob/2017wk48/sys-utils/setarch.8
> >
> > And that branch also has FIXME item near FDPIC_FUNCPTRS description.
> > Proposal(s) welcome how to make that text understandable.
>
> What about this text:
>
> "Treat user-space function pointers to signal handlers as pointers
> to address descriptors. This option has no effect on architectures
> that do not support FDPIC ELF binaries. Turns on FDPIC_FUNCPTRS."
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2017-12-11 13:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 12:51 [PATCH 1/4] vipw: do not let editor to inherit open file descriptors Sami Kerola
2017-12-03 12:51 ` [PATCH 2/4] rename: use access(3) to check if a file exists Sami Kerola
2017-12-04 12:05 ` Karel Zak
2017-12-03 12:51 ` [PATCH 3/4] docs: improve setarch(8) manual page Sami Kerola
2017-12-03 13:29 ` Dmitry V. Levin
2017-12-04 12:04 ` Karel Zak
2017-12-04 13:20 ` Sami Kerola
2017-12-09 1:29 ` Dmitry V. Levin
2017-12-10 10:54 ` Sami Kerola
2017-12-11 15:06 ` Karel Zak
2017-12-11 13:46 ` Karel Zak [this message]
2017-12-03 12:51 ` [PATCH 4/4] setarch: minor code clean up Sami Kerola
2017-12-04 12:06 ` Karel Zak
2017-12-04 12:05 ` [PATCH 1/4] vipw: do not let editor to inherit open file descriptors Karel Zak
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=20171211134653.wthtrktw373udxdw@ws.net.home \
--to=kzak@redhat.com \
--cc=kerolasa@iki.fi \
--cc=util-linux@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).