From: ron@ronnatalie.com (Ron Natalie)
Subject: [TUHS] Moto and MMU issues -- was Unix & Memory Management Units (MMU)
Date: Thu, 8 Dec 2016 11:38:44 -0500 [thread overview]
Message-ID: <07a801d25171$8b473660$a1d5a320$@ronnatalie.com> (raw)
In-Reply-To: <CAC20D2NV7DOaejq5_EHc52jh90HLjXeNkboSn_9wVFd_XYzYjw@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
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.
When we ported UNIX to the Denelcor HEP supercomputer, we had only a single base-offset segment (albeit 64 bits). The data and stack were allocated from that. In fact, the “stack” was a linked list.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20161208/ac89eaee/attachment.html>
next prev parent reply other threads:[~2016-12-08 16:38 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 [this message]
2016-12-08 17:12 ` Chet Ramey
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='07a801d25171$8b473660$a1d5a320$@ronnatalie.com' \
--to=ron@ronnatalie.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).