Rodney M Dyer wrote: > I've recently been in a rather elevated conversation with our help desk > manager about the OpenAFS web site. Our help desk manager had created > instructions for our Mosaic customers for installing OpenAFS on their > laptops and home machines. The instructions called for going to the > OpenAFS web site and downloading the "latest" OpenAFS client version and > installing it using his specified config. This would be all well and > good except that the "latest" OpenAFS version is always in flux and some > of our users, not knowing any better have been picking the developer > builds and release candidates. The developer builds and release > candidates have not been installing and have been having errors when the > AFS service started.
What page are you pointing them at? I would suggest http://www.openafs.org/windows.html for Windows clients and http://www.openafs.org/macos.html for MacOS X. Those pages always summarize the current STABLE, STABLE Candidate, and Development builds for end users. There is nothing we can do to prevent users from installing software that has bugs. We need people to install the software to find the bugs and report them. > I told our help desk manager to just download the one that we feel is > the most production and stable copy, put it on our own web site, and > point the users to our site. He said that he had done that in the past > but the version he kept on his site became "out of date" because he > rarely got around to updating it. This has been especially problematic > in the last couple of years since the versions have been increasing so > fast. I suspect that you want to vet a release for your organization, customize it with a Transform to default to uncc.edu and include any local files that you want to distribute, and then point your users to a local download site. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
