The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Phil Budne <phil@ultimate.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Project Idea: The UNIX Programmer's Manual: Heritage Edition
Date: Wed, 20 Sep 2023 23:48:19 -0400	[thread overview]
Message-ID: <202309210348.38L3mJDD097031@ultimate.com> (raw)
In-Reply-To: <CAP2nic3VBCCSkFS+NW517yNOeASxoRiswSFyYa2G45P6oHGboA@mail.gmail.com>

Adam Thornton:
> Say what you will about VMS, its HELP functionality makes it much easier to
> go from "I want to do X" to "And here's a sequence of commands that will do
> X" when you don't already have a good mental model of what's on the system.

I'm reminded of two fourty-odd year old diatribes(*) against Unix
documentation, yet somehow the Unix model has persisted, while other
systems have long since been taken out with yesterdays ashbin of history.

My beef, coming from TOPS-20 with VMS "HELP" was that (in the days on
having a single dumb terminal on your desk) was if you couldn't
remember a switch midway through typing a command you had to erase it,
wade through multiple levels of HELP screens, cancel out of that, and
then type the switch, until you realized you needed another switch.
On TOPS-20 you just typed ?

Yes, I suppose Unix-like systems could have section of pages with
overviews of functional areas (tho to be fair, v6/v7 era Unix didn't
have any facilities complex enough to warrant such things).

And it depends on which Unix-like system: "man 4 inet" on FreeBSD is a
more useful intro to TCP/IP socket programming than anything I can
find on my Ubuntu 22.04 system.  However, the FreeBSD man page
(unhelpfully) references two 4.3 BSD Interprocess Communication
Tutorials with no obvious information on how to find them.

(*) For diatribe #1 search for: "Last night I dreamed that the Real
World had adopted the Unix Philosophy".  For #2 search for "it's
literally a five-foot shelf of documentation"

  parent reply	other threads:[~2023-09-21  3:48 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
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 [this message]
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=202309210348.38L3mJDD097031@ultimate.com \
    --to=phil@ultimate.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).