The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: chet.ramey@case.edu (Chet Ramey)
Subject: [TUHS] Moto and MMU issues -- was Unix & Memory Management Units (MMU)
Date: Thu, 8 Dec 2016 12:12:43 -0500	[thread overview]
Message-ID: <a3d8efbf-e2fc-1e0e-63c0-96f96a202f53@case.edu> (raw)
In-Reply-To: <07a801d25171$8b473660$a1d5a320$@ronnatalie.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]

On 12/8/16 11:38 AM, Ron Natalie wrote:
> /
> 
> The original Bourne Shell did not use malloc, but rather had a SIGSEGV handler
> that used to extend the "string stack" called "stak" via sbrk() whenever the
> code tried to access data beyond the end ot the heap./
> 
> / /
> 
> The V6 (Mashey) shell did that.   I thought they’d gotten rid of that by
> the time the Bourne Shell rolled around.

That was one of the changes Bourne made during the deliberations over
which shell would be the Unix "standard" for Bell Labs.  It was always
an efficiency hack, meant to address Mashey shell user concerns about
performance.

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


  reply	other threads:[~2016-12-08 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 16:29 Clem Cole
2016-12-08 16:38 ` Ron Natalie
2016-12-08 17:12   ` Chet Ramey [this message]
2016-12-09 10:25     ` Joerg Schilling
2016-12-09 11:20       ` Paul Ruizendaal
2016-12-09 12:13       ` arnold

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=a3d8efbf-e2fc-1e0e-63c0-96f96a202f53@case.edu \
    --to=chet.ramey@case.edu \
    /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).