Ian McDonald wrote:
What about latest netdev tree rather than 2.6.13.2?
There have been changes going on...
Yep..but the answer is always to try one later build..and
it takes time (I reported similar problems in 2.6.11 and was
told that 2.6.12 (or maybe .13) was going to fix it...)
I am afraid that if I go to the effort to reproduce the problem
in 2.6.14, someone is just going to tell me to try the latest
pre-15 code.
Unless you are going to provide full bug reports etc then you have to
work off the latest tree for networking which is currently Dave
Miller's netdev tree.
So, I am asking the TSO folks: Will you pay any attention to
a bug report against 2.6.13.2, or would I just be wasting my
time?
If the answer is yes, then I'll get on it..otherwise, I'll wait untill
I move to a newer kernel version...
Developers are just like you - they don't have unlimited time either
and are often unpaid.
I'll buy the limitted time thing, but being unpaid is a lame excuse,
and probably not even generally true for the core developers.
Thanks,
Ben
--
Ben Greear <[EMAIL PROTECTED]>
Candela Technologies Inc http://www.candelatech.com
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
