Martin Webster wrote:
Since you made the comment, what was it in my original post that makes you say I "don't have the know how to explain what the cause is"? Considering the fact that in my original post I did say that it made sense not to mount them during the install, it seemed pretty obvious that I do have the "know how" to explain it. In that case, I find your comment a baseless, personal attack on my professional compentence. I sincerely hope that was not your intent, but I do find it hard to read anything else from that comment.
I think you're over reacting a little here. It was you afterall who publically directed critism ("[he] was completely unprofessional") at a SuSE employee. Furthermore, you haven't convinced me that there is a bug; software that does not display a characteristic that you'd expect to see does not necessarily constitute a bug. And providing an explanation is not the same as identifying the cause... Anyway bug reports should be sent to feedback@suse.de.
I apologise if I've caused you any grief. That was not my intention.
Oranges and apples. I have proof/evidence of his unprofessional behaviour: the comment. There was no evidence or indication of any lack of technical or professional compentence. I manage a hotline, I am writing a book on the subject and I would consider myself an expert in the field. In my professional experience, every hotline manager would say that telling a customer you are annoyed, whether justified or not is unprofessional. Maybe you tolerate comments like that, I don't and would never allow one of my employees to behave that way toward a customer, whether or not they actually paid for support. Saying that I "don't have the know how to explain what the cause is either" is completely baseless. The cause **was** the upgrade, regardless of the reason. The fstab is a not so unimportant file and it **should** be common knowledge to SuSE that people do, in fact, make changes to it based on their own invididual needs. Making significant changes to an important system file and neither backing up the file or saying that the change was made could have some serious effects on the system. IMHO that's a bug. At the very least it is not something I would expect from a company that is trying to market itself as a business solution. It was the feedback address that the original "bug" report was sent to and where the IMHO unprofessional comment came from. That is, the place that was annoyed that I didn't pay for the priviledge of reporting a (IMHO) bug. regards, jimmo