From: Dan Cross <crossd@gmail.com>
To: Warner Losh <imp@bsdimp.com>
Cc: segaloco <segaloco@protonmail.com>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Project Idea: The UNIX Programmer's Manual: Heritage Edition
Date: Wed, 20 Sep 2023 11:40:50 -0400 [thread overview]
Message-ID: <CAEoi9W7dhr0ghat7czJCi_4o8Dm2eQYvMjwLMsdtwDiA=wEs_g@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfrjehMHg3gVPhNhxFSDJbhKziCFsTd2s2hoCqP0xoQStg@mail.gmail.com>
On Wed, Sep 20, 2023 at 10:57 AM Warner Losh <imp@bsdimp.com> wrote:
> [snip]
> 4.4BSD almost certainly had some history. All the current BSDs have a HISTORY section for many of their pages. And we are busy borrowing each other's primary research for them... though it a man page, not a treatis on the evolution of signals since V7. Nor do the vast majority of command line flags have mention. Those that do are either 4BSD vs System V or XXXBSD vs Linux (and maybe a few FooBSD vs BarBSD, but those are rare).
My recollection is that the HISTORY stuff started showing up in BSD
man pages around the time of Net/2?
- Dan C.
next prev parent reply other threads:[~2023-09-20 15:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 20:32 [TUHS] " segaloco via TUHS
2023-09-19 23:39 ` [TUHS] " Larry McVoy
2023-09-20 1:26 ` segaloco via TUHS
2023-09-20 1:30 ` segaloco via TUHS
2023-09-20 14:57 ` Warner Losh
2023-09-20 15:40 ` Dan Cross [this message]
2023-09-20 2:09 ` Clem Cole
2023-09-20 2:25 ` Adam Thornton
2023-09-20 2:50 ` segaloco via TUHS
2023-09-20 19:56 ` Larry McVoy
2023-09-20 20:52 ` segaloco via TUHS
2023-09-20 22:31 ` Dave Horsfall
2023-09-21 4:09 ` Wesley Parish
2023-09-21 13:08 ` John P. Linderman
2023-09-21 0:26 ` Marc Donner
2023-09-21 3:06 ` Adam Thornton
2023-09-21 3:30 ` G. Branden Robinson
2023-09-21 3:48 ` Phil Budne
2023-09-21 13:37 ` Theodore Ts'o
2023-09-20 21:15 ` Alan Coopersmith
2023-09-21 3:49 ` G. Branden Robinson
2023-09-19 23:43 ` Adam Thornton
2023-09-20 13:23 ` Chet Ramey
2023-09-20 14:12 ` Alejandro Colomar (man-pages)
2023-09-19 23:47 ` KenUnix
2023-09-20 6:16 ` Jeremy C. Reed
2023-09-20 7:19 ` markus schnalke
2023-09-21 15:53 ` Kenneth Goodwin
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='CAEoi9W7dhr0ghat7czJCi_4o8Dm2eQYvMjwLMsdtwDiA=wEs_g@mail.gmail.com' \
--to=crossd@gmail.com \
--cc=imp@bsdimp.com \
--cc=segaloco@protonmail.com \
--cc=tuhs@tuhs.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).