From: schily@schily.net (Joerg Schilling)
Subject: [TUHS] Origin year of BSD csh?
Date: Mon, 27 Jun 2016 12:31:04 +0200 [thread overview]
Message-ID: <57710068.Y5JOWn5FNyxO2PxU%schily@schily.net> (raw)
In-Reply-To: <CAC20D2N1gHSsQYNCmUixdK4D5hhbfMuyD7wnYPmvD-3dTgtV7Q@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]
Clem Cole <clemc at ccc.com> wrote:
> A few years later, I did switch to typing to the csh when I got to UCB, but
> that was not until after the MIT job control stuff had been spliced into
> the BSD kernel (Horton & Kleckner were probably the ones that convinced me
> to learn it). With job control I became a fan, but never warmed up to the
> programming syntax. I picked up the mantra that I still consider wise --
> "type to Joy and program to Bourne." This is comfortable for the ROMS in
> the muscles of my fingers, but my scripts are portable.
Job control of course was an important improvement. I took the idea and
implemented in my bsh in 1985.
Now looking back, it is interesting, that there are just four shells that
implement support for vfork():
- csh - the first
- bsh since 1985
- ksh vfork() probably since 1984, jobcontrol apparently since 1982.
- bosh (my recent Bourne Shell) since 2014
But on a decent OS, vfork() helps a lot to speed up the shell.
On Solaris, fork() is copy-on-write based but still 3x slower than vfork().
Jörg
--
EMail:joerg at schily.net (home) Jörg Schilling D-13353 Berlin
joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'
next prev parent reply other threads:[~2016-06-27 10:31 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-26 10:14 Aharon Robbins
2016-06-26 16:30 ` Mary Ann Horton
2016-06-26 18:14 ` Larry McVoy
2016-06-26 18:32 ` Ronald Natalie
2016-06-26 20:43 ` John Cowan
2016-06-27 0:59 ` Larry McVoy
2016-06-27 1:11 ` John Cowan
2016-06-27 11:27 ` Sven Mascheck
2016-06-27 12:47 ` Steve Nickolas
2016-06-27 14:58 ` Joerg Schilling
2016-06-27 15:29 ` Ronald Natalie
2016-06-27 16:22 ` John Cowan
2016-06-27 16:35 ` Steve Nickolas
2016-06-27 20:00 ` Dave Horsfall
2016-06-27 20:33 ` Ronald Natalie
2016-06-27 20:44 ` Clem Cole
2016-06-27 21:02 ` Steve Nickolas
2016-06-27 21:15 ` Ronald Natalie
2016-06-27 21:20 ` John Cowan
2016-06-27 21:28 ` Ronald Natalie
2016-06-27 21:45 ` John Cowan
2016-06-28 6:49 ` Peter Jeremy
2016-06-28 7:51 ` arnold
2016-06-27 21:29 ` Random832
2016-06-28 14:47 ` Tony Finch
2016-06-26 19:41 ` Clem Cole
2016-06-27 10:31 ` Joerg Schilling [this message]
2016-06-27 13:01 ` Ronald Natalie
2016-06-27 13:15 ` Steffen Nurpmeso
2016-06-27 15:17 ` Joerg Schilling
2016-06-27 13:39 ` [TUHS] Bizarre job control, was csh Warren Toomey
2016-06-27 15:00 ` Steve Nickolas
2016-06-27 15:13 ` Joerg Schilling
2016-06-27 15:23 ` Steve Nickolas
2016-06-26 20:58 ` [TUHS] Origin year of BSD csh? Steve Nickolas
2016-06-27 10:03 ` Joerg Schilling
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=57710068.Y5JOWn5FNyxO2PxU%schily@schily.net \
--to=schily@schily.net \
/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).