From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] Another "craft" discussion topic - mindless tool proliferation
Date: Thu, 21 Sep 2017 17:36:24 -0700 [thread overview]
Message-ID: <20170922003624.GL25650@mcvoy.com> (raw)
In-Reply-To: <20170922000207.GB64682@eureka.lemis.com>
On Fri, Sep 22, 2017 at 10:02:07AM +1000, Greg 'groggy' Lehey wrote:
> On Thursday, 21 September 2017 at 20:39:24 +0200, Steffen Nurpmeso wrote:
> > Tony Finch <dot at dotat.at> wrote:
> >
> >> 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.
>
> There was a good reason for that. To my recollection, they hadn't
> been maintained At All, and they were decades out of date. While they
> were interesting for their historical content, as user/programmer
> documentation they were useless at best and misleading or dangerous at
> worst.
That's really on the maintainers, it's a shame they haven't kept those
up to date. Either update them or add to them, there has to be something
worth writing up.
I used to *love* those manuals.
next prev parent reply other threads:[~2017-09-22 0:36 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
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 [this message]
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=20170922003624.GL25650@mcvoy.com \
--to=lm@mcvoy.com \
/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).