Steven,

> It's not quite correct that I assume the standard image will 
> be w/out a module I was using and that was changed. My assumption
> was that you could make your own module dependent on a given
> version of another module. If that were the case, I could take
> my application that depends on MorphicKernel version A and
> NetworkingKernel version A, and change it so that it works
> with NetworkingKernel version Z but still use MorphicKernel
> version A (even if other applications in the same image 
> are using the newer MorphicKernel version Z).

This is not too far off and exactly the thing that Jecel was referring
to with having multiple versions of the same module running. It's
possible to do something like it but I think this is still a bit in the
future.

Cheers,
  - Andreas