The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Chet Ramey <chet.ramey@case.edu>
To: John Cowan <cowan@ccil.org>, Larry McVoy <lm@mcvoy.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] ksh88 source code?
Date: Tue, 21 Dec 2021 11:47:13 -0500	[thread overview]
Message-ID: <dbc12c7d-3d72-b18a-7ade-6c54de308664@case.edu> (raw)
In-Reply-To: <CAD2gp_RAYxkeTpxtHGyNCiMYauzEv_mJceoTswNirWGL2Y48Lw@mail.gmail.com>

On 12/21/21 11:42 AM, John Cowan wrote:
> 
> 
> On Tue, Dec 21, 2021 at 11:22 AM Larry McVoy <lm@mcvoy.com
> <mailto:lm@mcvoy.com>> wrote:
> 
>     I get the historical interest, but in today's world, is there any
>     advantage to ksh over bash?  I get that lots of scripts are run
>     with /bin/sh and it is nice when that is fast, but aren't the cpus
>     fast enough these days that it sort of doesn't matter?
> 
> 
> Ubuntu chose it as the default shell for sysvinit startup scripts in 2006
> (from which it spread to BSD) precisely because it was much faster than
> bash.  It's also smaller: bash is a memory hog. 

You're talking about dash, I think.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

  reply	other threads:[~2021-12-21 16:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-22 22:43 Warren Toomey
2020-12-22 23:01 ` Clem Cole
2020-12-23  1:29   ` John P. Linderman
2020-12-23 22:57     ` Warren Toomey
2020-12-23  3:30 ` Rico Pajarola
2020-12-23  9:03   ` Thomas Paulsen
2020-12-23  9:14     ` Rico Pajarola
2020-12-23  5:46 ` Scot Jenkins via TUHS
2020-12-23  7:19   ` Efton Collins
2021-12-21 13:55     ` Cyrille Lefevre via TUHS
2021-12-21 16:21       ` Larry McVoy
2021-12-21 16:27         ` Warner Losh
2021-12-21 17:15           ` Grant Taylor via TUHS
2021-12-21 17:31             ` Boyd Lynn Gerber
2021-12-21 19:09               ` Richard Salz
2021-12-22  6:23             ` jason-tuhs
2021-12-24 22:51               ` Grant Taylor via TUHS
2021-12-24 23:15                 ` Richard Salz
2021-12-24 23:34                 ` Michael Huff
2021-12-21 16:42         ` John Cowan
2021-12-21 16:47           ` Chet Ramey [this message]
2021-12-21 17:09             ` John Cowan
2021-12-22 11:11           ` Cyrille Lefevre via TUHS
2021-12-21 22:15         ` Thomas Paulsen
2021-12-22  7:44           ` arnold
2021-12-22 14:35           ` Cyrille Lefevre via TUHS
2021-12-22 14:36             ` Chet Ramey
2021-12-23 13:39       ` [TUHS] Bourne shell source code (was Re: ksh88 source code?) Cyrille Lefevre via TUHS
2020-12-23  6:56 ` [TUHS] ksh88 source code? arnold
2021-12-22 14:40 Norman Wilson
2021-12-23 17:23 ` John Cowan
2021-12-23 20:08   ` silas poulson
2021-12-23 19:10 Norman Wilson

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=dbc12c7d-3d72-b18a-7ade-6c54de308664@case.edu \
    --to=chet.ramey@case.edu \
    --cc=cowan@ccil.org \
    --cc=lm@mcvoy.com \
    --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).