Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: segaloco <segaloco@protonmail.com>
Cc: Paul Winalski <paul.winalski@gmail.com>,
	"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 13:32:52 -0400	[thread overview]
Message-ID: <CAC20D2Nvb0cEH0Zusfma6Hik25pNZPSU8snGGb0NoS9wfrQ2uA@mail.gmail.com> (raw)
In-Reply-To: <u_dX3zKg0jmM7HQvXxjvZH3CLS9E4mHx4XgfpN3dK5c4hfXX8TJA9iqIdv-jeB_8BRfjNjCET9IGfk2fHJWOAcy2F7KkCDUSn51-GbLtkIE=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 945 bytes --]

On Tue, Jun 13, 2023 at 1:05 PM segaloco via COFF <coff@tuhs.org> wrote:

> The permuted index is surprisingly useful in this regard but isn't always
> there in manpage sources, you'd have to generate it.
>
Indeed.  @Doug do you know who was the brilliant person that came up with
that tool and built the first UNIX PTX? I always felt they should be lauded
for that piece of work!

It was something that when I first learned about UNIX that I did like.   I
was primarily coming from TOPS and TSS, and UNIX was strange when I first
saw it -- cat instead of print or type, of course, being the first
roadblock.   But when I found the PTX was one of the first times that
"light dawned on marble head."

I saw UNIX long before "learn" was released, but I certainly had helped
enough new users by the time it was available that the "learn" tool, a
printed copy of the man pages, and PTX were where I told "newbies" to start.
ᐧ

[-- Attachment #2: Type: text/html, Size: 2248 bytes --]

  reply	other threads:[~2023-06-13 17:33 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
2023-06-13 17:32                   ` Clem Cole [this message]
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=CAC20D2Nvb0cEH0Zusfma6Hik25pNZPSU8snGGb0NoS9wfrQ2uA@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=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).