To read all comments associated with this story, please click here.
With all due respect, it does not show persistence for the original developers, or much of anything good about them, really: any bug of this sort that's known about to cause data loss/corruption is generally considered a "no-ship" bug everywhere I've been, and this bug shows also that they simply didn't do very good testing and think about all the reasonably possible edge cases, and this existed for 25 years until some puzzled developer victimized by it tracked it down in a short time period. Kudos the developer that tracked this down: raspberries at the one(s) that should have caught and fixed this ages ago (how many generations does that count in when it comes to this field? ACK!)
I think this illustrates the fallacy of the "many eyeballs" meme that is taken as the gospel truth in open source circles.
Here, we have a bunch of open source developers (samba) who find a flaw in an open source product (BSD) and instead of stepping through the BSD source tree to find the problem, they code a samba hack that works around the problem on BSDs. In fact, it appears they didn't even submit a bug report.
Guess what? This happens all the time in the closed source world. If we come across a bug in someone else's code, we code a temporary hack around the problem and wait for the bug to be resolved. This article suggests that such development culture appears in open source projects too, which is understandable.
I hope that naive open source advocates who keep preaching the "many eyeballs" meme will stop doing so. The majority of developers do not have the desire or the inclination to fix other peoples bugs even if the source is available. Hell, it seems that some don't even file bug reports...





Member since:
2008-03-16
NOT as old as I am. But I am glad to hear that it eventually got fixed. Shows Persistence and Dedication, if nothing else.