Jeffrey Altman <[EMAIL PROTECTED]> wrote: > Rodney M Dyer wrote: >> The developer builds and release >> candidates have not been installing and have been having errors when >> the AFS service started. > > I feel compelled to point out the fact that I have seen zero bug > reports saying that OpenAFS would not install or that the service > would not start (except on Windows Vista and that is because of bugs > in Vista.)
I fill bug reports (although I haven't had any service crashes recently.) Everything I filled against the Windows client (and possibly the Solaris server, but still testing) seems to be fixed in the latest fc. > What would be really helpful is if there were a group of people who > would volunteer to act as testers for each release. If we had a > volunteer for each platform who would agree to test each release with > a few days and report back the results, that would be so beneficial to > the community. It would also allow the Gatekeepers to focus on other > things. I can (and have been trying to as often as possible) test clients on Windows 2003 Server (SP1 and SP2 beta x86) as they are released. I do not currently have any 64-bit OSes running nor do I have any machines running Windows XP or Windows 2000. If no one else has the time, I can setup test systems in a VM and make sure a basic install works, but I would not be actively using software in these VMs. I would assume that testing in actual environments would be preferable. Also, I typically use the Windows cmd prompt myself and don't notice GUI issues (which is why I didn't notice that the explorer extention was broken until a week ago. Its been broken on my installs for several months.) <<CDC -- Christopher D. Clausen [EMAIL PROTECTED] SysAdmin
smime.p7s
Description: S/MIME cryptographic signature
