Re: tlug: Ethernet timeout problem

["Stephen J. Turnbull" <turnbull@example.com>]

>>>>> "NIIBE" == NIIBE Yutaka <gniibe@example.com> writes:

    NIIBE> Rex Walters writes:
    >> Bypassed the "determine the problem is really in the driver"
    >> and "*admit* the problem is really in the driver" stages
    >> altogether.

    NIIBE> Could you please explain the reason why you think so?  Do
    NIIBE> you have any rationale why my judgement may be wrong?

Oh, no, no!  :-)

In this case, "bypass" means simply 「飛ばす」 but not 「逃げる」 or 
「さぼる」.  It can mean the latter, but here it means "avoid a
bottleneck" (like in Boris Yeltsin's heart surgery).

What he meant is that normally (especially with proprietary products),
the user says "couldn't it be the driver?" and the programmer says,
no, it's a hardware problem.  So the user studies the driver code, and
finds the bug.  Then there is a week-long flame-war, and finally the
programmer admits that there is a problem with the code.

Rex forgot to mention that the programmer will then refuse to accept
the user's patch, and spend another two weeks trying to find a better
one.  Then after that it takes a week to find a patch which is really
the same as the user's patch, but doesn't look like it.

Anyway, your post honestly admits the possible problem with the driver
and saved us three weeks of programming effort and a flame war.  This
is not normal, but ...

Rex LIKES that.  :-)

---------------------------------------------------------------
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