The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: tfb@tfeb.org (tfb@tfeb.org)
Subject: [TUHS] Emacs and undump
Date: Mon, 27 Feb 2017 12:59:01 +0000	[thread overview]
Message-ID: <23910FC1-18D7-4B5F-8DF3-28CFBAEEDC6C@tfeb.org> (raw)
In-Reply-To: <86y3wsp0cq.fsf@molnjunk.nocrew.org>

On 27 Feb 2017, at 07:19, Lars Brinkhoff <lars at nocrew.org> wrote:
> 
> Emacs came from ITS, and many Lisps derive from Maclisp which also came
> from ITS.  In ITS, it was common for applications to be dumped into a
> loadable core image, even if they were written in assembly language.

I think the history of this must go back beyond ITS.  InterLisp did the same thing, and it's a west-coast Lisp so probably not influenced by ITS (and it probably predates ITS in its beginnings).  So either the idea was just pervasive (which is at least plausible I think) or it has its roots somewhere further back: I wonder what Lisp 1.5 did?

Oddly I once learned something important about TCP because of this.  I had a Xerox D-machine (an 1186, which was a Daybreak I think), which I needed to move somewhere.  I was logged into it and running a Lisp image with lots of state, so I did whatever incantation was needed to write all the dirty pages to disk halt Lisp, turned the machine off and carried it wherever it needed to go, plugged power and network back in and restarted the image.  Unbeknownst to me I had a couple of telnet windows open to Unix machines: when I turned the machine back on they were not only still open but they still had live sessions in them.

Well, it seems obvious now, but that was the moment when I understood how TCP worked.

--tim


  parent reply	other threads:[~2017-02-27 12:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.334.1488132096.3779.tuhs@minnie.tuhs.org>
2017-02-26 19:16 ` David
2017-02-26 19:28   ` Mantas Mikulėnas
2017-02-27  6:41   ` Tim Bradshaw
2017-02-27  7:19     ` Lars Brinkhoff
2017-02-27  7:26       ` Warner Losh
2017-02-27  8:12         ` Nick Downing
2017-02-27 14:33           ` Derek Fawcus
2017-02-27 14:50             ` Nick Downing
2017-02-27 15:43               ` Derek Fawcus
2017-02-27 16:43             ` Joerg Schilling
     [not found]               ` <CAH1jEzZjvOhHnbvsWcw8gbx9d_W47DbBidYd_tteCr5dC6H2ng@mail.gmail.com>
2017-02-28  0:02                 ` Nick Downing
2017-02-27 12:59       ` tfb [this message]
2017-02-27 10:35   ` Joerg Schilling
2017-02-27 15:13     ` Tony Finch
     [not found] <mailman.342.1488180370.3779.tuhs@minnie.tuhs.org>
2017-02-27 10:24 ` Johnny Billquist
2017-02-27 10:30   ` Lars Brinkhoff
2017-02-27 10:47     ` Johnny Billquist
2017-02-27 14:04       ` Arthur Krewat
2017-02-28 11:55         ` Ronald Natalie
     [not found] <mailman.346.1488208394.3779.tuhs@minnie.tuhs.org>
2017-02-27 20:09 ` Johnny Billquist
2017-02-27 20:26   ` Lars Brinkhoff
2017-02-27 21:06     ` Johnny Billquist

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=23910FC1-18D7-4B5F-8DF3-28CFBAEEDC6C@tfeb.org \
    --to=tfb@tfeb.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).