🚀 go-pugleaf

Memory protection this, memory protection that. Simply read_protecting
LoadSeg'ged CODE segments would be quite a boost. Likewise, read & write
protecting all memory on the freelist would be a big help. Of course,
performing the latter would probably run out of memory segment descriptors
mighty fast unless AllocMem() was rewritten. Sure, apps could still wildly
trash system-common data structures like ExecBase, but it would be a big
step forward in preventing tasks from corrupting other tasks & free memory.
-djh
+----------------------------------------------------------------------------+
| Dallas J. Hodgson               |     "This here's the wattle,             |
| Metaphor Computer Systems       |      It's the emblem of our land.        |
| Mountain View, Ca.              |      You can put it in a bottle,         |
| USENET : djh@metaphor.com       |      You can hold it in your hand."      |
+============================================================================+
| "The views I express are my own, and not necessarily those of my employer" |
+----------------------------------------------------------------------------+