"Stephen J. Turnbull" <stephen(a)xemacs.org> wrote:
I don't think good support for unexec across the board is in the
cards, though.
Oh, yes, and it just gets worse with newer 64-bit systems (as
someone's got to port/twiddle unexec). For these, it's often easier to
just use pdump.
I don't think this has much advantage over redumping from
scratch,
except saving a couple of megabytes of disk space per instance on
single user systems.
Well, this *is* the same as redumping from scratch, except that the
user can then tell XEmacs to use his (private) pdump image.
It's not a matter of saving some trivial amount of disk space --
it's a matter of being able to do it at all. Note that, for some
systems, unexec doesn't work, and so pdump has to be used. Now, if you
have root access, and you're the only one using the workstation, there's
probably no problem; you just rebuild XEmacs using the current
procedures (but also include additional stuff via site-load, etc.).
However, if you don't have root access, or are on a multi-user system,
then specifying a pdump image is the only way (which you currently
cannot do).
AFAIK even with pdump you need to dump with the
same temacs you are going to reload into, so if you tried to have a
system xemacs and per user dumpfiles, you'd still force the users to
redump on every system update.
Yup, this is a definite problem, and there's currently no solution
for this.
--
Darryl Okahata
darrylo(a)soco.agilent.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.