fork() idea

[Robert Collins]

Just running this past for criticism.

What if on fork(), we loaded a _trivial_  stub program, what depends on
little-or-nothing, and thus takes up almost no memory, has little chance
of dll conflicts, address relocation etc. Then allocate memory to look
like the parent, load .dll's etc.

The point of this being that it allows a neat hack:
System shared memory can be made copy on writewith FILE_MAP_COPY. On
WinNT, if we load the application image into system mapped memory, we
can then duplicate much/most of the address space with _much_ lower
overhead.

Thoughts?

Rob