The 03.04.28 at 13:53, Avi Schwartz wrote:
The thing is that I did post this last week and received no replies from anyone. Maybe no one else on this list uses the same NIC?
I didn't read it till you mentioned here, but the solution wouldn't have occurred to me. I thought it was a driver bug.
I do feel though that SuSE's support policies should be discussed openly and not just in emails directly to SuSE. People should know what level of support (or lack of) they are getting when they purchase a SuSE package.
Me too. The list is about Suse Linux, and support is part of it, I think. IMO, SuSE should be more sensitive to these problems, specially when the user complains of something that could be more or less general, or even a bug in the supplied product, files, books, whatever. I have received better advice on this list :-) Mind you, I think suse makes probably the best distribution, or almost so, and I have bought it for years. But I think the support they give is insufficient - and before somebody says that I could buy more support, I'd say that I shouldn't have to pay anything for getting support or at least some help or advice on bugs/errors that are not mine. I think it goes with the warranty - again, in my opinion :-) The response "not covered by..." reminds me of a job I had at a telephone company by a contractor. If the complaint came with missing fields, we rejected it without reading, even if we new the solution. Policy from above :-( -- Cheers, Carlos Robinson