Dean Anderson <[EMAIL PROTECTED]> writes: > The afs_syscall interface can, I expect, always be statically linked in > even if a kernel doesn't offer dynamic system calls.
Uh, where did you get static linking from? I don't remember ever statically linking an AFS kernel module on Solaris. What are we even talking about at this point? You're describing a method of handling kernel interfaces that I don't recognize at all. > On systems that can support both interfaces dynamically, this isn't a > problem, and there is no need. But on systems that can't do both > dynamically, you will need a syscall module that can be statically > linked, and you will need a dynamically loaded driver module. The only systems I know of that need static linking need it for *any* kernel module, regardless of what it's doing. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> _______________________________________________ OpenAFS-devel mailing list OpenAFS-devel@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-devel
