on GUIs and such things

[Jonathan S. Shapiro]

> EROS' approach is to isolate corruption within a single domain and
> memory leaks within the children of a single spacebank.

Neither of these statements is relevant to persistence in EROS. The problem
is that this statement is mixing a couple of levels of abstraction.

For purposes of understanding persistence, the only code we care about in
EROS is the kernel. If a domain is bad, EROS will guarantee that it is still
bad on reboot.

In practice, storage leaks may or may not be restricted by the spacebank
hierarchy in a useful sense, because I may write a program that accesses
storage from a spacebank that you provide. In the future, we may also permit
lateral transfers of space between consenting banks -- MarkM worked out how
to do this.

> Also, you can't entirely prevent memory leaks; if you don't overwrite
> unused pointers, you will still have them in Lisp or Java.

Sure you can:

    su
    killall -9 java

Works like a charm! Gives you cycles back to do *useful* things, too!