[quanah]

Originally Posted by z00dax

quanah, I take it from your signature that you are fairly high on the food chain - so I recommend you do a few things. Start by reading the original post here : CentOS is NOT supported

I've read the post many times.

I suggest you start with the initial thread:
first installation ZCS 5.0GA on centos 4.6 failed

where users describe running into problems installing 5.0.0_GA on CentOS4.6. That is what prompted the entire discussion.

There is ZERO technical merit in that statement and in that post, there is nothing that says that its RHEL-4 he is talking about. Including vague stuff like "
We've identified that the issue is not with Zimbra, but rather CentOS." does not help the situation since its not backed up with *any* technical facts, if you guys really do have a clue what you are talking about, highlight the issue so someone can do something about it, rather than making generic statements that really just amount to FUD.

What we identified is that only users of CentOS4 were reporting hitting the problem. On RHEL4, we don't have the issue. I.e., we were clearly able to identify that the problem was not specifically with the Zimbra 5.0.0_GA release.

I again suggest you read the OP, the issue whatever it is was identified by your people and isolated aparently by them. Perhaps you guys should talk a bit more amongst yourselves as well ?

I'm not sure what you mean here. I'm the one who has been working on the issue. I've been working with John Holder to make sure he knew what things we had or had not identified in a given period of time.

The only reason we are here in your forum to clear the FUD you are creating is because we have had a number of users come back and say there is an issue somewhere. I dont use the product, but I know there are users who do. As I have already said in my previous post to this thread, identify an issue and we can try to fix it, if you dont have an issue - shut up and stop creating FUD.

BTW, you might be interested in knowing that your people have already privately admitted to testing on CentOS. Which I would presume makes sense. Perhaps you are just not aware of this testing ? Again, communication breakdown within Zimbra ?

I don't believe we've created any FUD. Our users reported a problem with a specific operating system. As noted, we only officially test (QA) on RHEL. Yes, some people use CentOS internally on their own systems. However, those are not part of our QA process. So what they use internally for their own stuff is completley immaterial.

I dont see how someone might confuse that to imply that 'RHEL works but CentOS does not'.

Because the problem being reported was only happening on CentOS4 and not reproducible on RHEL4. Plus as I've noted, RHEL4 and CentOS4 definitely differ in their XS support.

I think what needs to happen here is that the original post needs to clear out a bit with real facts, and an apology that the guy was clueless who posted that statement saying CentOS does not work : would go a long way down that path.

You want the original user who posted that he was hitting issues with CentOS 4.6 to say they were clueless and issue an apology? I think that's stretching things a bit. They hit a real problem. What do they have to apologize for?

On the other hand, if there really is a problem in the CentOS-4 packages, you need to point out what the problem is, since if the OP is to be believed, Zimbra has already identified what the issue is. And we can work with you on fixing it. Also, as I have already stated, I dont use Zimbra, but I know there are a lot of users on CentOS who do - and it might be worth everyone's effort if the issue, if there is one, was resolved.

As I said, I myself have been unable to reproduce it. So far, no one has been able to provide me a system that has the issue so that I can look at it. So, do real users on CentOS seem to be running into an issue? Yes. Can I reproduce it? No. Do I have a system on which the problem has occurred to examine? No. Would I like to know for sure that CentOS4 doesn't have the problem, or identify what the issue is, so it can be fixed? Of course. That's why I've taken the time to look at it.

--Quanah