From: steffen@sdaoden.eu (Steffen Nurpmeso)
Subject: [TUHS] Another "craft" discussion topic - mindless tool proliferation
Date: Thu, 21 Sep 2017 20:39:24 +0200 [thread overview]
Message-ID: <20170921183924.oaj23%steffen@sdaoden.eu> (raw)
In-Reply-To: <alpine.DEB.2.11.1709211829040.2486@grey.csi.cam.ac.uk>
Tony Finch <dot at dotat.at> wrote:
|Lyndon Nerenberg <lyndon at orthanc.ca> wrote:
|>> On Sep 19, 2017, at 4:35 PM, Theodore Ts'o <tytso at mit.edu> wrote:
|>>
|>> If you take a look at how perl handles its man pages, with 188 man
|>> pages in section 1:
|>
|> ... you quickly recognize the difference between a manpage (i.e.
|> reference page) and a user manual.
|
|I think it's a shame that the non-man-page parts of the Unix documentation
|set have been neglected, in that you don't often get newer programs
|following the style of the USD / SMM / PSD guides.
The problem being that even FreeBSD dropped them from the base
system. I think only NetBSD still ships with it. And Linux never
had that stuff anyway, only thanks to the dedicated Linux
man-pages project it is that you have anything usable at all (when
not sticking with the GLibC info manual). I do not want to be
back in 1999 when i desperately searched for just about anything
but copyright notices in /usr/share/doc (or /usr/doc, i forgot),
and that should be /usr/share/copyrights still for most of the
things.
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
next prev parent reply other threads:[~2017-09-21 18:39 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 17:01 Jon Steinhart
2017-09-19 17:05 ` Steve Nickolas
2017-09-19 20:31 ` Pete Turnbull
2017-09-19 20:37 ` Warner Losh
2017-09-19 23:35 ` Theodore Ts'o
2017-09-20 0:47 ` Lyndon Nerenberg
2017-09-20 1:02 ` Larry McVoy
2017-09-20 1:09 ` Lyndon Nerenberg
2017-09-20 1:13 ` Larry McVoy
2017-09-20 1:22 ` Larry McVoy
2017-09-20 2:01 ` Larry McVoy
2017-09-20 2:34 ` Bakul Shah
2017-09-20 2:47 ` Larry McVoy
2017-09-20 6:18 ` Bakul Shah
2017-09-20 4:35 ` Grant Taylor
2017-09-20 5:54 ` Ian Zimmerman
2017-09-24 23:03 ` Ralph Corderoy
2017-09-24 23:35 ` Bakul Shah
2017-09-20 16:49 ` Steffen Nurpmeso
2017-09-20 4:29 ` Grant Taylor
2017-09-20 6:43 ` Peter Jeremy
2017-09-20 8:25 ` Bakul Shah
2017-09-20 9:12 ` Steve Nickolas
2017-09-20 9:34 ` Bakul Shah
2017-09-20 16:48 ` Steffen Nurpmeso
2017-09-20 2:07 ` Theodore Ts'o
2017-09-24 22:58 ` Ralph Corderoy
2017-09-20 4:26 ` Grant Taylor
2017-09-20 16:45 ` Steffen Nurpmeso
2017-09-21 17:33 ` Tony Finch
2017-09-21 18:39 ` Steffen Nurpmeso [this message]
2017-09-22 0:02 ` Greg 'groggy' Lehey
2017-09-22 0:30 ` Lyndon Nerenberg
2017-09-22 0:38 ` Larry McVoy
2017-09-22 0:39 ` Lyndon Nerenberg
2017-09-22 0:50 ` Larry McVoy
2017-09-22 1:01 ` Lyndon Nerenberg
2017-09-22 1:08 ` Larry McVoy
2017-09-22 20:09 ` [TUHS] remaking make (Re: " Bakul Shah
2017-09-22 2:25 ` [TUHS] " Warner Losh
2017-09-22 3:26 ` Greg 'groggy' Lehey
2017-09-22 4:09 ` ron minnich
2017-09-22 2:20 ` Warner Losh
2017-09-22 0:36 ` Larry McVoy
2017-09-22 0:40 ` Lyndon Nerenberg
2017-09-22 1:53 ` Michael Parson
2017-09-22 3:25 ` Grant Taylor
2017-09-20 6:20 ` Lars Brinkhoff
2017-09-20 16:39 ` Steffen Nurpmeso
2017-09-24 22:54 ` Ralph Corderoy
2017-09-25 0:16 ` Steve Johnson
2017-09-25 11:30 ` Ralph Corderoy
2017-09-20 18:15 ` Clem Cole
2017-09-20 18:35 ` Jon Steinhart
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=20170921183924.oaj23%steffen@sdaoden.eu \
--to=steffen@sdaoden.eu \
/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).