Date: Sun, 30 May 1999 20:06:59 -0700 (PDT) From: Jaye Mathisen <mrcpu@internetcds.com> To: Mike Smith <mike@smith.net.au> Cc: Dennis <dennis@etinc.com>, Bill Paul <wpaul@skynet.ctr.columbia.edu>, hackers@FreeBSD.ORG Subject: Re: xl driver for 3Com Message-ID: <Pine.BSF.4.10.9905301957450.219-100000@schizo.cdsnet.net> In-Reply-To: <199905302150.OAA12070@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
It is kind of interesting that now the shoe is on the other foot... A few months ago I purchased some sync cards from ET, and had some (and am still having) trouble getting them to work consistently. When I emailed their support dept for help, I got a few curt non-helpful replies, then a message about how if I didn't understand every nuance of HDLC, and couldn't read the debugging output of his cards/software, then I was (my interpratation, not his words exactly) not worth of his effort, nor his company's products. I have offered access to the boxes for the trivially repeatable problem I am having, in order so that he can improve his product, but the answer so far is "Try a new version of the software". The shotgun approach to tech support. It is no wonder that he does not invest effort in helping the 3com driver work better, he is unwilling to work with a customer with a significant dollar amount invested in his boards make *his* product better, why would he be worried about improving others product, he has little interest in improving his own. Which is too bad, because when it works, it (the ET board) works just great. When it doesn't, don't ask ET for help. What you get is a lot of talking down, what you don't get is real help. On Sun, 30 May 1999, Mike Smith wrote: > > >> I have no stake in 3com cards (they are > > >> problematic in LINUX as well)...maybe the cards are flawed? Its not my > > >> problem. > > > > > >It *is* your problem. Supposing you can't get Intel cards anymore. > > >Then what're you going to do. > > > > Use something else that works. If none of them work then FreeBSD is no > > longer a viable option. > > This is the core fallacy; you should restate this as: > > "If none of them work, then FreeBSD is no longer a viable option > because it will require me to do some work to help fix them". > > I'm sorry; the FreeBSD Project is dedicated to developing operating > system code, not wiping your ass. You've received abundant offers of > assistance requiring no more than minimal effort on your part, and > turned them all down. This kind of selfish laziness is something we > can all do without. > > -- > \\ The mind's the standard \\ Mike Smith > \\ of the man. \\ msmith@freebsd.org > \\ -- Joseph Merrick \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9905301957450.219-100000>