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
| Andrew Morton | -mm merge plans for 2.6.23 |
| Rafael J. Wysocki | [Bug #11207] VolanoMark regression with 2.6.27-rc1 |
| Zhang, Yanmin | AIM7 40% regression with 2.6.26-rc1 |
| Con Kolivas | [PATCH][RSDL-mm 0/7] RSDL cpu scheduler for 2.6.21-rc3-mm2 |
git: | |
| Gregory Haskins | [RFC PATCH 03/17] vbus: add connection-client helper infrastructure |
| David Woodhouse | [PATCH 03/30] solos: FPGA and firmware update support. |
| Natalie Protasevich | [BUG] New Kernel Bugs |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
