The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Project Idea: The UNIX Programmer's Manual: Heritage Edition
Date: Wed, 20 Sep 2023 01:30:37 +0000	[thread overview]
Message-ID: <5RzxjSGC9j4riL9Kr7cVp4UwTY2SVNxyNxQNG5RCZLh874BzbGP9ZS5U7IErArwrvMm6Ii40GhHK7n009tpnToX78D-3MQSt9xx2XqDnKuc=@protonmail.com> (raw)
In-Reply-To: <NsBxoM3Fmx3TRX-QtiMzmlpE6cxoN46_gPrz3BFC7UeagaeRB3RCTm8LjjWruqgK76o-m0Rr4oBOMGbq8c7WgPZAIvuzv_2bxlw8yMlhITE=@protonmail.com>

> > I'd start with groff.
> > 
> > So I'm a little off topic but if people wanted to work on that, I'd be
> > up for that project. It's not as big as what you are saying but it's
> > pretty big, I think we just start with something, see if we can get
> > debian/ubuntu to pick it up, lather, rinse repeat. In fact if we
> > just get the groff project to pick up our stuff, all the distros will
> > get that eventually.
> > 
> > --
> > ---
> > Larry McVoy Retired to fishing http://www.mcvoy.com/lm/boat
> 
> 
> That's an excellent point, the beauty of UNIX being a granular system is that such an effort wouldn't need to be a "start at page 1 and finish at page whatever", but could be done piecemeal. Groff would also be a great candidate due to the preponderance of supporting secondary papers, like the NROFF/TROFF manual, different macro definitions, etc. That does then get into the prospect of the secondary papers too, likewise excellent references to this day on a number of subjects that I personally would love to have modernized versions of.
> 
> Well if anyone catches wind of such a project kicking off in some way elsewhere, know that I'm certainly interested in what I can contribute. What my work towards this eventual goal will probably continue to look like for now though is just doing my diff analysis of manual versions, as one of my principle goals there was to identify the apparent last common ancestor of Research, PWB, and BSD lineages, at least as far as documentation is concerned. Common sense would just say research V7 but there are little tidbits here and there between V6 and V7 that don't show up in other places, just tiny little nuanced things for the most part. I haven't done this part of the analysis at all but a causal glance at a 32V manual diffed with a V7 manual reveals some changes that don't appear to be related to the portability work. But I'm not going to comment on that further without analysis to back it up, just some anecdotal observations at present.
> 
> > Why (and when) did GNU drop the HISTORY section from its man pages?
> > 
> > Adam
> 
> 
> Did GNU ever have a HISTORY section? I just plucked a couple books off the shelf, I don't see HISTORY in the V10, 4.4BSD, or SVR4 books, so probably a later invention in the BSD line that didn't get picked up by other UNIX-likes? Looking at a few illumos manpages, they also don't appear to have a HISTORY section. They appear to be there on macOS, probably as a result of the FreeBSD origins of macOS user space. That said, I also appreciate the HISTORY section, it's tipped me off to things to study that I didn't know on a few occasions.
> 
> - Matt G.

Sorry for the double bump, don't want to lie, just found a few pages in the 4.4BSD manual with a HISTORY section.  Checked the same pages in V10, SVR4, and 4.3BSD, no dice, so maybe 4.4BSD at the earliest?  Of course I could just grep this but where's the fun in that (and I'm not at a computer I have a UNIX tree on right now...)

- Matt G.

  reply	other threads:[~2023-09-20  1:30 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 [this message]
2023-09-20 14:57       ` Warner Losh
2023-09-20 15:40         ` Dan Cross
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='5RzxjSGC9j4riL9Kr7cVp4UwTY2SVNxyNxQNG5RCZLh874BzbGP9ZS5U7IErArwrvMm6Ii40GhHK7n009tpnToX78D-3MQSt9xx2XqDnKuc=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=segaloco@protonmail.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).