On 6/1/07, Jan Kalcic <[EMAIL PROTECTED]> wrote:
Andrew Beekhof wrote: > But you're wasting my time and that annoy me. > > I don't have all day to pry relevant information out of people. > "it works for him but not me", yet you didn't think to mention the > version difference? > > Thats pretty relevant don't you think? Especially since it means the > problem, whatever it was, is clearly already resolved and all you need > to do is upgrade (or follow Dejan's advice at the time which was > almost certainly correct). > Don't keep on pushing this. I told you which is the version.
Over a month after your original post. Dude, you're my hero. Stop being lazy and use some common sense. You wouldn't call up a mechanic and say: "My car broken. My friend has a car and it works fine! What's wrong?" So don't do the IT equivalent.
Do you think I have time to waste? You wrong man.
No, but you clearly think OSS developers do.
I've just said to Tom, the guys who opened the thread, that even if I updated my sles10 it didn't work for me. Dejan's advice was "stop heartbeat before modify cib.xml"
he advised more than that
and it was a very important advice (thanks Dejan once again) but the cib.xml which eventually worked was the one he passed me because, once again, the one I generated with version 2.0.7 didn't work for me. Are you saying it doesn't work properly?
No. What I said is that the problem with the generation step appears to be fixed in 2.0.8
Then, you should know that this is the latest version available from suse.
I know very well what version is the latest from SUSE. I also know that the first thing their support network will tell a customer is to reproduce any problems on the latest available version.
Andrew Beekhof wrote: > please update to the latest version available from suse via the update > service Once again, it doesn't solve the problem!
An upgrade didn't solve your problem but, since Tom's problem is in no way related to yours, it could quite conceivably solve his.
> If you want vendor support for older versions then you need to go via > the proper channels, and community mailing lists ain't one of them. Don't say update to the latest version available from suse then.
First of all, I made that comment to Tom, not you. Secondly, regardless of where the packages come from my advice to people running older versions is the same as pretty much every OSS project out there: "upgrade to the latest available version". Projects don't release new versions just for fun. Thirdly, whether the upgrade solves this particular problem is irrelevant, the advice is valid as his cluster will be unsupported by SUSE until he does. Lastly, the point - which you missed entirely - was that if you want a vendor package updated then you should contact the vendor and not hijack unrelated threads on a community list to complain about bugs that have already been fixed.
> The lesson people, is that you're not going to get a response if you > don't give enough information on which to do so. And there is no > excuse for not knowing what to send because its at the bottom of every > single email sent to the list: > Ohhh, very interesting lesson.
Sorry? You don't care enough about a problem to provide even the most basic information about it - yet when we take the same attitude regarding your "request" it's somehow unfair is it? Amazing. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
