Douglas E Engert <[EMAIL PROTECTED]> writes: > Its actually knowing what the syscall is that AFS uses to set the PAG. > and what to do if the syscall fails. You don't really have to link in > any AFS library. The pam_afs2 does this, and uses no AFS or Kerberos > libs.
> It would be nice AFS provided a header file or picked up the pam_afs2. Yeah, you can do it that way too right now, but I don't want to assume that we're always going to use a system call or that it's always going to be as simple as calling syscall. I can imagine possible future changes (particularly with Linux, where adding syscalls is a pain in the ass) where this might not necessarily be the case. I think a simple shared library is a better long-term solution for providing the interface than just a header file, since it can then cope with such changes and should have an exceedingly stable API. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
