The 25-Year-Old BSD Bug
sproketboy writes with news that a developer named Marc Balmer has recently fixed a bug in a bit of BSD code which is roughly 25 years old. In addition to the OSnews summary, you can read Balmer's comments and a technical description of the bug.
"This code will not work as expected when seeking to the second entry of a block where the first has been deleted: seekdir() calls readdir() which happily skips the first entry (it has inode set to zero), and advance to the second entry. When the user now calls readdir() to read the directory entry to which he just seekdir()ed, he does not get the second entry but the third. Much to my surprise I not only found this problem in all other BSDs or BSD derived systems like Mac OS X, but also in very old BSD versions. I first checked 4.4BSD Lite 2, and Otto confirmed it is also in 4.2BSD. The bug has been around for roughly 25 years or more."
...of the superiority of Microsoft.
but they had more important things to do. At least until Balmer started throwing chairs.
Of course, now that I've R'd the FA, I understand that it's the first entry in the block (of which a directory with a sufficient number of files would have multiple), and not the first entry in the directory. Kindly ignore my previous response... Nothing to see here...
an existential philosopher turned empiricist perhaps?
-1 not first post
This is the power of Open Source!
With all those eyes looking at the code, stuff like this gets ID'd and fixed LICKITY SPLIT!
(runs and hides)
If you want news from today, you have to come back tomorrow.
Bug tracking software missed this because it's bug #1. lol.
If no one has cared enough to fix it for 25 years, I'm guessing this should be rated as "inconsequential."
Must have been a really slow news day at OSNews.
Invenio via vel creo
If you define BSD as a collection of bugs, this story proves that BSD is dying.
--
make install -not war
After this long would this not be considered a feature? :)
My Web Site - www.ocean-liners.com
3 thoughts on this:
1. I think this bug would be classified "archeological".
2. The question now is what happens to the Samba work-around patches. Now that the bug is fixed, do the patches cause a side-effect (i.e. "a new bug")?
3. This gives rise to a new meme of nerd insults. "You call yourself a programmer? Why I've fixed bugs older than you!" Of course, only one man is entitled to use that line.
No, this story proves that BSD is dying because there was a bug in it and no complaints were heard for 25 years.
Indeed. Not surptisingly nobody was really interessted.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
(In other words, I believe in all things moderation and think zealotry is absurd and I probably shouldn't be confused with an open source zealot or even an advocate.)
Sounds like you're a bit of a moderation zealot...
Not A Sig
except for the code parts from Xenix (which is 28 years old) that was renamed to "SCO Unix" in 1989, which was - as we all know - stolen and illegally put completely into linux... (we have a suitcase full of evidence!!!)
The MAFIAA is a bunch of mindless jerks who will be the first up against the wall when the revolution comes
Paul Anderson
"I drank WHAT?!" -- Socrates
Surly a bug this old should be reclassified as a scrab beetle?
That's "scarab" beetle, and don't call me Surly.
But complaints are heard NOW !
What does this mean ?
Resurrection ?