The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron minnich <rminnich@gmail.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: crt0 -- what's in that name?
Date: Tue, 13 Jun 2023 09:37:26 -0700	[thread overview]
Message-ID: <CAP6exY+fzPVi1gES8fDNs90sGO02tzieU8npmO_EFUOjW4B47A@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2306131519040.16633@aneurin.horsfall.org>

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

thanks all. In 1976, at udel, we thought it meant c runtime startoff and
that seems to be a reasonable interpretation.

Kind of nice that a very new system, oreboot, will have a bt0 performing
about the same function :-)

On Mon, Jun 12, 2023 at 10:28 PM Dave Horsfall <dave@horsfall.org> wrote:

> On Mon, 12 Jun 2023, Clem Cole wrote:
>
> > > I've always thought of it as "C run time stage 0".
> >
> > crt - C RunTme.   I always heard it expressed as C  runtime SYSTEM or
> > START
>
> Ah; well, I was almost right :-)  It's been a while since I was using
> Ed 5 where I first saw that comment...
>
> -- Dave

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

  reply	other threads:[~2023-06-13 16:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 18:22 [TUHS] " ron minnich
2023-06-12 18:29 ` [TUHS] " Dan Cross
2023-06-12 18:53   ` Clem Cole
2023-06-12 19:45     ` segaloco via TUHS
2023-06-12 20:03       ` Chris Pinnock via TUHS
2023-06-12 20:22         ` Dan Cross
2023-06-12 20:28           ` Chris Pinnock via TUHS
2023-06-12 20:58             ` Paul Winalski
2023-06-12 21:32               ` segaloco via TUHS
2023-06-12 21:28             ` Anthony Martin
2023-06-12 20:25         ` Steve Nickolas
2023-06-12 20:17   ` Dave Horsfall
2023-06-12 21:31     ` Clem Cole
2023-06-12 21:39       ` G. Branden Robinson
2023-06-12 22:39         ` Clem Cole
2023-06-12 22:50           ` G. Branden Robinson
2023-06-12 23:04           ` Paul Winalski
     [not found]             ` <20230612234953.pwu7oi6hyglsaqzs@illithid>
     [not found]               ` <CABH=_VTv1g76MnHQpkOPXRu9WFe2Kc8qchJbAgTCMpv0bFzUrQ@mail.gmail.com>
2023-06-14  1:59                 ` [TUHS] Re: [COFF] " Adam Thornton
2023-06-12 22:09       ` [TUHS] " Paul Winalski
2023-06-13  5:28       ` Dave Horsfall
2023-06-13 16:37         ` ron minnich [this message]
2023-06-13  0:46 Douglas McIlroy
2023-06-13  1:37 Norman Wilson
2023-06-13  1:41 ` Rob Pike
2023-06-13  1:48 ` Dan Cross
2023-06-13 10:03 Rudi Blom
2023-06-13 12:10 Douglas McIlroy

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=CAP6exY+fzPVi1gES8fDNs90sGO02tzieU8npmO_EFUOjW4B47A@mail.gmail.com \
    --to=rminnich@gmail.com \
    --cc=dave@horsfall.org \
    --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).