The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] run commands at login in v6 and stty
Date: Sat, 26 Feb 2022 17:49:07 -0500	[thread overview]
Message-ID: <CAC20D2P=zWYy2uJazgVKEbT_234Ox0uBZwBFjme-R_bHYTNb5Q@mail.gmail.com> (raw)
In-Reply-To: <acd97ce7-5827-56ba-aec2-6cf4dbb41169@gmail.com>

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

Some thoughts ..

1.) the precursor to the csh is the newshell in {1}BSD.  It's Joy's hack to
the Thompson shell and you might find it more usable.
2.) PWB 1.0 is based on a V6 kernel and has the Mashey Shell, which is in C
and predates Bourne's  It might also be easier for you to use.
3.) srb wrote his shell during the transition between V6, TS and V7.   At
least one version ran on the V6++ system we had at CMU, but of course as
pointed out, it is written in Bourne-Gol. And I'm pretty sure his CPP
definitions will need at least a gen2 /lib/cpp implementation***  However,
Steve was also doing it at the time when the compiler was being updated.
FWIW: We also had the 'Typesetter C' running on our V6 system in those
days.  So my >>guess<< is that v6 + Typesetter C - will compile the V7
shell.

Clem



*** Rob or Steve Johnson - maybe remembers when cpp first appeared.  I
don't remember if it was part of V5 or not - those bits have faded from my
brain.  What I do remember is there were a couple of different cpp's early
on.  The first one was pretty crude by today's standards, albeit it was a
cool idea and it was the one thing I really liked about C over BLISS early
on [BLISS had Macros, which was cool aalso, but cpp could do things Bliss
could not].

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

  parent reply	other threads:[~2022-02-26 22:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-26 20:39 Will Senn
2022-02-26 21:03 ` Michael Kjörling
2022-02-26 22:49 ` Clem Cole [this message]
2022-02-26 23:12   ` Rob Pike
2022-02-27  0:46     ` Clem Cole
2022-02-27 15:01     ` Larry McVoy
2022-02-27 17:10       ` Clem Cole
2022-02-26 21:45 Brian Walden
2022-02-26 22:16 ` Rob Pike
2022-02-27 20:32 ` Sven Mascheck
2022-02-27  7:48 Noel Chiappa
2022-02-28  1:04 Douglas McIlroy
2022-02-28  7:22 ` Rob Pike
2022-02-28 14:07   ` Larry McVoy
2022-02-28 18:47     ` Dan Cross
2022-02-28 19:25       ` Dan Cross
2022-02-28 21:25         ` markus schnalke
2022-02-28 19:26       ` Clem Cole
2022-02-28 20:03         ` Adam Thornton
2022-02-28 18:18 ` Warner Losh

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='CAC20D2P=zWYy2uJazgVKEbT_234Ox0uBZwBFjme-R_bHYTNb5Q@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=tuhs@minnie.tuhs.org \
    --cc=will.senn@gmail.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).