Some of the crypto framework modules have multiple linkages, primarily for legacy reasons. For example misc/sha1 and crypto/sha1 are just hard links to the same binary that has a misc linkage and a crypto linkage.
Is it possible during the modules own _init() to know which linkage caused us to be loaded ? The reason I'd like to determine this is because the modules register with the crypto framework (misc/kcf) during their _init() which causes misc/kcf to be pulled in and quite a lot of work happens in setting up kcf. If we can avoid that it would be useful. The misc/sha1 misc/md5 modules are sometimes needed very early in boot so avoiding dragging in kcf and having it setup is useful thing to avoid if we can. misc/kcf has its own way of causing the modules to get loaded when they are needed. I suspect this isn't possible and if it isn't we can continue as we are just now by letting misc/kcf startup. -- Darren J Moffat _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
