From: segaloco via COFF <coff@tuhs.org>
To: Paul Winalski <paul.winalski@gmail.com>
Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
Computer Old Farts Followers <coff@tuhs.org>
Subject: [COFF] Re: [TUHS] Re: crt0 -- what's in that name?
Date: Tue, 13 Jun 2023 17:04:39 +0000 [thread overview]
Message-ID: <u_dX3zKg0jmM7HQvXxjvZH3CLS9E4mHx4XgfpN3dK5c4hfXX8TJA9iqIdv-jeB_8BRfjNjCET9IGfk2fHJWOAcy2F7KkCDUSn51-GbLtkIE=@protonmail.com> (raw)
In-Reply-To: <CABH=_VTv1g76MnHQpkOPXRu9WFe2Kc8qchJbAgTCMpv0bFzUrQ@mail.gmail.com>
> But man pages are utterly useless if your question is
> "what command do I need to use to do X?"
The permuted index is surprisingly useful in this regard but isn't always there in manpage sources, you'd have to generate it. There are the technical memoranda too, starting with V6 those were distributed with the manpages from what I know. Research and BSD kept them packed in to the end but USG took them out starting with System V presumably to make more paper documentation sales. The technical papers still hold a lot of value imo and render much of the literature out there redundant. They're my preferred source of "how do I do xyz" even if 1000 books have been published on the same subject.
- Matt G.
next prev parent reply other threads:[~2023-06-13 17:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP6exYKUbHjLJm=PNuxtzF49NfOc3q1rpkRLeGqaPpp-=RwFTw@mail.gmail.com>
[not found] ` <CAEoi9W4DJXEXfr=iMOnTQVedHzcOamPyvpWy413j3_=dXrMB1g@mail.gmail.com>
[not found] ` <alpine.BSF.2.21.9999.2306130615560.16633@aneurin.horsfall.org>
[not found] ` <CAC20D2PiOh-p48G83ChUYZnfHTdNXROcJsewwmbM1xnyrt4c9w@mail.gmail.com>
[not found] ` <20230612213912.mywv5znz66pk3n5q@illithid>
2023-06-12 22:39 ` Clem Cole
2023-06-12 22:50 ` G. Branden Robinson
2023-06-12 22:57 ` Clem Cole
2023-06-12 23:04 ` Paul Winalski
2023-06-12 23:49 ` G. Branden Robinson
2023-06-13 16:28 ` Paul Winalski
2023-06-13 17:04 ` segaloco via COFF [this message]
2023-06-13 17:32 ` Clem Cole
2023-06-13 17:02 ` [COFF] Re: UNIX and its users - new or old Clem Cole
2023-06-14 13:33 ` Dan Cross
2023-06-14 15:39 ` Clem Cole
2023-06-14 22:13 ` Dan Cross
2023-06-15 4:20 ` Adam Thornton
2023-06-15 12:13 ` Dan Cross
2023-06-12 23:57 ` [COFF] Weedhopper? (was: crt0 -- what's in that name?) Greg 'groggy' Lehey
2023-06-13 0:30 ` [COFF] " G. Branden Robinson
2023-06-13 3:07 ` Clem Cole
2023-06-13 3:05 ` Clem Cole
2023-06-13 3:26 ` Bakul Shah
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='u_dX3zKg0jmM7HQvXxjvZH3CLS9E4mHx4XgfpN3dK5c4hfXX8TJA9iqIdv-jeB_8BRfjNjCET9IGfk2fHJWOAcy2F7KkCDUSn51-GbLtkIE=@protonmail.com' \
--to=coff@tuhs.org \
--cc=g.branden.robinson@gmail.com \
--cc=paul.winalski@gmail.com \
--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).