Why lib/interp.c?

[Rob Landley]

This overrides the shared libraries' path to the shared library loader.  
Question: why do blah.so files even _have_ a path to the shared library 
loader?  Don't you already need a shared library loader running in order to 
be able to load the suckers in the first place?  Why can't that one work 
recursively?

I'm confused.  Each executable can only have one shared library loader, even 
when it links against a dozen shared libraries.  So all the libraries an 
executable links directly against have to be able to be loaded by the same 
shared library loader.  Why should the libraries it links _indirectly_ 
against be any different?

What's the point here?

Rob
-- 
"Perfection is reached, not when there is no longer anything to add, but
when there is no longer anything to take away." - Antoine de Saint-Exupery