Path: utzoo!attcan!uunet!pyrdc!pyrnj!rutgers!ucla-cs!srt
From: srt@maui.cs.ucla.edu (Scott Turner)
Newsgroups: comp.sys.apollo
Subject: Re: undump/preloaded tex on apollo domain systems
Message-ID: <16115@shemp.CS.UCLA.EDU>
Date: 21 Sep 88 19:30:42 GMT
References: <8809211216.AA02990@umix.cc.umich.edu>
Sender: news@CS.UCLA.EDU
Reply-To: srt@cs.ucla.edu (Scott Turner)
Organization: UCLA Computer Science Department
Lines: 37

GBOPOLY1@NUSVM.BITNET (fclim) writes:
>
>in article <16054@shemp.cs.ucla.edu>, scott turner (srt@cs.ucla.edu)
>writes:
>
>>described in an earlier message.  If you are *real* interested in
>>building a pre-dumped version, you might want to look at how GNU
>>Emacs works on the Apollos.
>
>i doubt if adding some code from gnu emacs to tex will help.  otherwise,
>we should also be able to have a preloaded emacs.

From the APOLLO file that comes with Zubkoff's Emacs fixes:

...
GNU EMACS is dumped during the building process by creating a freeze file
containing all of EMACS's impure state; the freeze file is called "emacs.dump"
and is stored in the "etc" directory named by PATH_EXEC in "paths.h".  If you
must rebuild EMACS for any reason, after performing the make in the "src"
directory you must move the file "temacs" to "../emacs" and the file
"temacs.dump" to "../etc/emacs.dump".

Note that in order for dumped EMACS's to function properly, you must have the
DOMAIN csh variable "inprocess" unset, so that executing EMACS causes a fresh
process to be created, and hence causes EMACS to be loaded at the same point in
memory as when it was dumped.  For this reason, you must also have "inprocess"
unset when you make EMACS.
...

So Emacs does do something like a dump/undump, leaving you with an 
executable preloaded Emacs.  Whether these changes would be difficult to 
apply to TeX I can't say.
					-- Scott Turner
 
    Scott R. Turner
    UCLA Computer Science     "Understanding 'em is Knowing how to Break 'em"
    Domain: srt@cs.ucla.edu