On Sun, 13 Apr 2008 20:47:30 +0200 Willy Tarreau <w@1wt.eu> wrote:That's because many (probably most) Linux bugs are dependent upon the hardware which they run on, and developers cannot reproduce the failure on their hardware. Other software products don't have that problem. That being said.. four or five years ago, developers would often work closely with the reporter working out why the reporter's failure was occurring. Several days of back-and-forth. We dont' do that as much nowadays - there's a tendency to a) throw the problem back at the reporter, often asking them to bisect. If the reporter is running a distro kernel (eg: Fedora) then that's quite hard, and often isn't a think they have knowledge to do. So they'll just disappear. Or b) just ignore the report altogether. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| debian developer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 014/196] kobject: remove incorrect comment in kobject_rename |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
| Stephen Rothwell | Re: Announce: Linux-next (Or Andrew's dream :-)) |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
| Radu Rendec | htb parallelism on multi-core platforms |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
