From mboxrd@z Thu Jan  1 00:00:00 1970
From: krewat@kilonet.net (Arthur Krewat)
Date: Mon, 27 Feb 2017 09:04:47 -0500
Subject: [TUHS] Emacs and undump
In-Reply-To: <95085781-7de7-1658-6150-ce9145d5ee49@update.uu.se>
References: <mailman.342.1488180370.3779.tuhs@minnie.tuhs.org>
 <145bd49e-7390-034b-f8c3-002e6e6f15fe@update.uu.se>
 <86mvd8orhm.fsf@molnjunk.nocrew.org>
 <95085781-7de7-1658-6150-ce9145d5ee49@update.uu.se>
Message-ID: <f5e54bab-fc7c-11cf-4ee4-a1c9dc459342@kilonet.net>

In TOPS-10, you could detach from your current job, login again, and 
keep going. Then, attach to the previous job, and go back and forth 
endlessly.

As for keeping memory around, it was very common on TOPS-10 to put code 
in a "hiseg" that would stick around, and was shareable between "jobs".

For something like EMACS, it would be very efficient to have the first 
person run it "compile" all the LISP, leave it in the hiseg, and other 
jobs can then run that code.

Not knowing anything about EMACS, I'm not sure that compiled code was 
actually shareable if it was customized, just thinking out loud.

But even without leveraging the hiseg capability, it was relatively easy 
to save an entire core image back to a .SAV or .LOW or later a .EXE. I 
don't remember how easy it was to do that programmatically, but it was 
easy from the terminal and if it saves a lot of processor time (and 
elapsed time) people would have been happy to do it manually.

On 2/27/2017 5:47 AM, Johnny Billquist wrote:
>
> Ah. It was so long ago, and I never learned ITS that well. However, I 
> don't think you can have several jobs in Tops-10, and I know you can't 
> in OS/8 or RT-11.
>
> But that's an interesting capability. To have several jobs around, 
> with the memory intact, and you can switch between them, and play with 
> their memory.
>
>     Johnny
>