From: Steve Litt <slitt@troubleshooters.com>
To: supervision@list.skarnet.org
Subject: Re: runit patches to fix compiler warnings on RHEL 7
Date: Wed, 4 Dec 2019 16:06:04 -0500 [thread overview]
Message-ID: <20191204160604.6beab715@mydesk.domain.cxm> (raw)
In-Reply-To: <20191204164014.dnp7zmgfdt42ats4@mink.imca.aps.anl.gov>
On Wed, 4 Dec 2019 10:40:14 -0600
"J. Lewis Muir" <jlmuir@imca-cat.org> wrote:
> On 12/04, Jonathan de Boyne Pollard wrote:
> > Jan Braun:
> >
> > > 2) runit has manpages. s6 has HTML. :(
> > >
> > Daniel J. Bernstein had something to say on that subject, two
> > decades ago. See the "Notes" section of
> > http://cr.yp.to/slashdoc.html .
> >
> > I generate both manual pages and HTML from a common DocBook XML
> > master in the nosh toolset. And the DocBook XML is itself readable
> > directly with a WWW browser.
> > http://jdebp.uk./Softwares/nosh/guide/commands/setuidgid-fromenv.xml
> > is a copy of one such DocBook XML master, for example. It's on the
> > WWW, and the packages also install it locally, for off-line
> > reading.
>
> I still like having man pages. It's often just easier to type "man
> <name>" than to find the local (or remote) HTML document and open it
> in a web browser.
I never thought about man pages until a few days ago I did some
experiments with execline and had a quick question about syntax. I did
man execlineb and of course got "no entry". So I fired up a browser,
did a locate command, and put a path in my browser.
The browser is vastly superior for learning all about
unfamiliar or moderately familiar software, but for the quick lookup of
something you primarily know about, there's no substitute for a quick
"man execlineb".
SteveT
Steve Litt
December 2019 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
next prev parent reply other threads:[~2019-12-04 21:06 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 21:43 J. Lewis Muir
2019-11-27 20:33 ` J. Lewis Muir
2019-11-28 7:59 ` Ben Franksen
[not found] ` <ecdf4d8f-93f6-3f9f-b84c-351fa91c7f02@uni-bremen.de>
2019-11-28 19:04 ` Laurent Bercot
2019-11-28 20:39 ` Steve Litt
2019-11-28 22:17 ` runit or s6 (was: runit patches to fix compiler warnings on RHEL 7) Laurent Bercot
2019-11-29 14:09 ` runit patches to fix compiler warnings on RHEL 7 Jan Braun
2019-11-29 21:46 ` Dewayne Geraghty
2019-11-30 1:22 ` Colin Booth
2019-11-30 0:21 ` Colin Booth
2019-11-30 3:14 ` Steve Litt
2019-11-30 13:32 ` Jeff
2019-11-30 13:46 ` Jeff
2019-11-30 10:15 ` s6 usability (was: runit patches to fix compiler warnings on RHEL 7) Laurent Bercot
2019-11-30 14:32 ` Jeff
2019-11-30 18:58 ` Laurent Bercot
2019-12-02 12:07 ` Jeff
2019-12-02 22:20 ` Laurent Bercot
2019-12-02 2:47 ` Steve Litt
2019-12-02 3:37 ` s6 usability Dewayne Geraghty
2019-12-02 10:24 ` fungal-net
2019-12-02 21:32 ` s6 usability (was: runit patches to fix compiler warnings on RHEL 7) Laurent Bercot
2019-12-02 23:17 ` s6 usability Samuel Holland
2019-12-03 22:10 ` Steve Litt
2019-12-21 11:49 ` Jan Braun
2019-12-04 12:15 ` Jonathan de Boyne Pollard
2019-12-04 21:02 ` Laurent Bercot
2019-12-04 1:30 ` s6 usability (was: runit patches to fix compiler warnings on RHEL 7) Casper Ti. Vector
2019-12-21 9:26 ` s6 usability Jan Braun
2019-12-21 18:36 ` Guillermo
2019-12-21 21:19 ` Colin Booth
2019-12-22 1:05 ` Jan Braun
2019-12-22 8:30 ` Colin Booth
2019-12-21 23:46 ` Laurent Bercot
2019-12-22 5:53 ` Jan Braun
2019-12-22 20:33 ` Steve Litt
2019-12-22 23:20 ` Laurent Bercot
2019-12-23 1:28 ` Oliver Schad
2019-12-23 9:14 ` Laurent Bercot
2019-12-23 10:15 ` Jonathan de Boyne Pollard
2019-12-24 0:18 ` Oliver Schad
2019-12-23 1:57 ` Steve Litt
2019-12-23 9:00 ` Laurent Bercot
2019-12-22 23:47 ` Dewayne Geraghty
2019-12-04 11:36 ` runit patches to fix compiler warnings on RHEL 7 Jonathan de Boyne Pollard
2019-12-04 16:40 ` J. Lewis Muir
2019-12-04 20:48 ` Laurent Bercot
2019-12-04 21:32 ` J. Lewis Muir
2019-12-04 21:06 ` Steve Litt [this message]
2019-12-04 21:50 ` Laurent Bercot
[not found] ` <20191205132736.7f501460@puter>
2019-12-08 19:10 ` Laurent Bercot
2019-12-02 17:57 ` J. Lewis Muir
2019-12-02 21:06 ` J. Lewis Muir
2019-12-02 22:22 ` Laurent Bercot
2019-12-02 21:58 ` Laurent Bercot
2019-12-03 10:57 ` Benjamin Franksen
2019-12-04 10:43 ` Jonathan de Boyne Pollard
2019-12-02 17:13 ` J. Lewis Muir
2019-12-04 11:13 ` Jonathan de Boyne Pollard
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=20191204160604.6beab715@mydesk.domain.cxm \
--to=slitt@troubleshooters.com \
--cc=supervision@list.skarnet.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).