[DGD] Object Manager missing some objects

Shentino shentino at gmail.com
Mon Mar 13 20:36:01 CET 2006


Currently, the only objects that are compiled before objectd are
kernel side stuff, libraries inherited by initd or objectd (and their
libraries ad nauseum).  Both are either off limits or deducible at
runtime so I'm not terribly worried.

Klib doesn't notify objectd when kernel clones are created/deleted
anyway, and non-kernel clones are easy to defer until objectd is set
up.

Make objectd the first object compiled by initd and you won't have
problems unless you're doing something REALLY weird.
On 2/6/06, Shentino <shentino at gmail.com> wrote:
> Since only the kernel is allowed to create or delete clones of kernel
> objects anyway, I really didn't see any need to bother with them.
> Kernelese clones are for me hands off and I dunnever mess with'em.
>
> Any reason why objectd would need to behave otherwise?
>
> On 2/6/06, Neil McBride <sarak at castinian.org> wrote:
> > > Wouldn't just iterating through the source files in /kernel be enough
> > > to keep track of all pre-objectd compilations?
> >
> > You could, but you wouldn't find clones that were created before the
> > object manager was initialised using such an approach - whether that's a
> > problem is up to you :)  You'd also miss anything that managed to be
> > compiled from a string, not that that's a problem with the kernel lib at
> > startup.
> >
> > Neil.
> >
> > PS. Sorry if this arrives twice - I think I sent the first one using the
> > wrong From address :D
> >
> >
> > __________________________________________
> > http://mail.dworkin.nl/mailman/listinfo/dgd
> >
>




More information about the DGD mailing list