The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] Etymology of bc(1)
Date: Fri, 12 Sep 2014 11:18:13 -0600	[thread overview]
Message-ID: <09F72555-089F-4BC4-A602-93CC5B51F0B0@bsdimp.com> (raw)
In-Reply-To: <5371bd291f9537ed5935435a418bc648.squirrel@webmail.yaccman.com>

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


On Sep 12, 2014, at 11:12 AM, scj at yaccman.com wrote:

> A gentle reminder that in that era, 4K words of memory cost in the 5
> digits of $'s, and many Unix machines had far less than the 64K bytes
> (yes, K) that was the maximum.  And there was no paging.  Piping was kind
> of a poor man's paging to write programs that would work on small-memory
> machines.
> 
> While there were benefits, it was also a big pain, especially when
> debugging.  And for the most part, we abandoned this style when we got
> 32-bit machines that had as much as a (gasp!) megabyte of memory...

Sure beat the heck out of trying to get overlays right. I remember “fondly”
trying to get the overlay layout manager working to get the FORTRAN programs
I was writing at the time to fit into 64k (or was it 48k). Switching from the PDP-11
to the VAX was a godsend and all that moved into the kernel and got way simpler
from the user perspective…

Warner

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20140912/10029b12/attachment.sig>


  reply	other threads:[~2014-09-12 17:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-12  1:54 Noel Chiappa
2014-09-12  2:35 ` Mark Longridge
2014-09-12  6:00 ` Dave Horsfall
2014-09-12 11:15   ` John Cowan
2014-09-12 11:36     ` Otto Moerbeek
2014-09-12 17:12       ` scj
2014-09-12 17:18         ` Warner Losh [this message]
2014-09-12 19:02         ` Clem Cole
2014-09-12 19:36       ` Dave Horsfall
2014-09-12 20:03         ` Warner Losh
2014-09-12 19:32     ` Dave Horsfall
2014-09-12 18:28 ` Tim Bradshaw
2014-09-13  2:52   ` Dave Horsfall
  -- strict thread matches above, loose matches on Subject: below --
2014-09-12  3:15 Noel Chiappa
2014-09-12  3:33 ` Larry McVoy
2014-09-12  6:10 ` Dave Horsfall
2014-09-11 21:24 Christian Neukirchen
2014-09-11 21:41 ` Warner Losh
2014-09-11 22:04   ` Dave Horsfall
2014-09-11 22:17     ` John Cowan
2014-09-11 23:34       ` scj
2014-09-12  1:03       ` Dave Horsfall
2014-09-12 13:37         ` random832
2014-09-12 14:18           ` Steve Nickolas
2014-09-12 20:02           ` Dave Horsfall

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=09F72555-089F-4BC4-A602-93CC5B51F0B0@bsdimp.com \
    --to=imp@bsdimp.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).