> Shared libraries for example don't look up stuff like this inside
> themselfs. (Unless you look at DLL stubs...)
Nor does the kernel. Internal symbols are already resolved
> It's the ld.so programm which maintains such data.
> modutils don't do anything different from classical late binding.
> The natural place for such maintainance work could be for example
> the init process, which serves already pretty a similar role for
Well actually the logical place to do it is in modutils. Which is where
we do it right now. We even precompute dependancies with depmod much like
the dynamic link caches
> Another analogy is the rpm dependency maintainance.
> It's the rpm program - which does checking here and not
> the actual application itself during the file-system install.
Actually for dynamic stuff the application also does some of it for late
binding and when triggers are used for relations between packages
All of which says the current modutils method is correct
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue May 07 2002 - 22:00:14 EST