If you have some free time and have autoconf and/or ddns experience, I have a project in mind which (while not OpenAFS-specific) may help speed the adoption of AFS generally.
The capsule summary is that there is already an AFS server which can safely export local filesystems read-only. It lacks autoconf support. Something else, which probably can and should be optional but which would really be a slam-dunk for this in some environments, would be DDNS support, namely, when the server starts, registers or updates an AFSDB record using DDNS, and undoes this when shutting down. That, however, is less important than autoconf support. The intent of this would be to put to rest arguments about "setting up an AFS server is too heavyweight for my needs, I just want to share some files". Combined with a client supporting AFSDB and dynroot/freelance, you have a simple readonly file sharing network. -D _______________________________________________ OpenAFS-devel mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-devel
