[EROS-Arch] Package handling...

[Joerg Bornschein]

On Mon, Mar 26, 2001 at 06:50:21PM -0800, Norman Hardy wrote:

> Here are some more thoughts of very similar problems.
> Alas few solutions however.
> <http://cap-lore.com/Software/LifeIsHard.html>
> The above may be of use for it relates the software library problems
> with several similar problems.
> There may be solutions to these other problems that I am unaware of.

I think the most important unsolved(?) problem is that constructors don't
know whether there are instances running or not.
This knowledge seems very important to allow software updates:
 One can easily build and distribute constructors with a new version
 of a service -- but one can't simply delete a constructor or the spacebank
 which holds the code segment.

The only solution i can currently think of is: each constructor manages a list
 of capabilities -- one capability into each product's memory build by 
 this constructor.
 If a product exits regulary, it must deregister itesef. If it's
 spacebank has been rescinded, the constructor knows this because
 his capability for this product has gone void.

I don't like this procedure.... :-(


> Share subroutine libraries are vary rare in Keykos except for those
> that Unix compilers expect. Function that an native Keykos
> application would use a library routine for is typically had by
> invoking a key.
> Math routines are the only thing that come to mind as warranting
> a shared library.

Oh, that partial brain dump wasn't about shared libraries. I expected
all factories to build services. Where did you get the impression i
was talking about shared libraries?


  joerg