Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: Ethernet timeout problem
- To: NIIBE Yutaka <gniibe@example.com>
- Subject: Re: tlug: Ethernet timeout problem
- From: Rex Walters <rex@example.com>
- Date: Thu, 23 Apr 1998 12:44:48 +0900
- Cc: tlug@example.com
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <199804230328.MAA17016@example.com>; from NIIBE Yutaka on Thu, Apr 23, 1998 at 12:28:17PM +0900
- Mail-Followup-To: NIIBE Yutaka <gniibe@example.com>, tlug@example.com
- References: <Pine.LNX.3.96LJ1.1b7.980422162244.9835L-100000@example.com> <199804220809.RAA28192@example.com> <199804230024.JAA12894@example.com> <19980423094731.61582@example.com> <199804230328.MAA17016@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
On Thu, Apr 23, 1998 at 12:28:17PM +0900, NIIBE Yutaka wrote: > Rex Walters writes: > > Bypassed the "determine the problem is really in the driver" and > > "*admit* the problem is really in the driver" stages altogether. > > Could you please explain the reason why you think so? Do you have any > rationale why my judgement may be wrong? Certainly, it may be wrong. > But please understand I answered by my experiences. If you would > explain how do you thought by my answer, I could learn more. > > I *did* determine the problem, and *did* admit the problem is really > in the driver. From the kernel message, I was pretty sure that the > problem is really in the driver. The problem was reported several > times (from all over the world), and I fixed occasinally. Please > search archives to check this. YES! Exactly! I'm sorry, you've misunderstood me. I was trying to compliment you for providing such excellent support. Really! Sarcasm is so difficult in email. I meant to poke fun at commercial vendor support organizations who often point the blame at everything else before they realize the problem really is with their own drivers. And then, even when they realize it, they hide the fact from the customer and take a long time to admit the problem. I tried to say that you determined and admitted the exact problem immediately, whereas (by implication) outside the Linux/Open-Source world this almost never happens. Please don't take my message as criticism in any way! Your quick, decisive, obviously knowledgeable response blew me away. One *never* gets that kind of response with proprietary non-opensource software. Best regards, -- Rex --------------------------------------------------------------- Next Nomikai: 15 May Fri, 19:30 Tengu TokyoEkiMae 03-3275-3691 Next TLUG Meeting: 13 June Sat, Tokyo Station Yaesu gate 12:30 Featuring Stone and Turnbull on .rpm and .deb packages --------------------------------------------------------------- a word from the sponsor: TWICS - Japan's First Public-Access Internet System www.twics.com info@example.com Tel:03-3351-5977 Fax:03-3353-6096
- References:
- Re: tlug: Ethernet timeout problem
- From: Scott Stone <sstone@example.com>
- Re: tlug: Ethernet timeout problem
- From: Tim Meggs <tim@example.com>
- Re: tlug: Ethernet timeout problem
- From: NIIBE Yutaka <gniibe@example.com>
- Re: tlug: Ethernet timeout problem
- From: Rex Walters <rex@example.com>
- Re: tlug: Ethernet timeout problem
- From: NIIBE Yutaka <gniibe@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: tlug: Ethernet timeout problem
- Next by Date: Re: tlug: Ethernet timeout problem
- Prev by thread: Re: tlug: Ethernet timeout problem
- Next by thread: Re: tlug: Ethernet timeout problem
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links