vnode Bug Fixed In OpenBeFS.
Jan 29, 2004 23:40 UTC, by Chris Simmons, Senior Journalist
From the  department...

This just in... deet deet deet..
 
The long-standing vnode bug in OpenBFS has finally been fixed (to about 90%), according to the rather excited Bruno "BGA" Albuquerque of the OpenBFS team.
 
Check out some of the chatroom log here:
 
"[18:03] Ok, as we are all good news today, the vnode bug in OpenBFS has been fixed!
[18:03] And this time for real!
[18:03] BGA : seriously!?
[18:03] WOO!
[18:03] awesome
[18:03] BGA : can I quote you on that?
[18:03] there should be a new release tomorrow... There is still a locking issue to be resolved.
[18:04] Yay! Now you can write that AIM protocol, BGA :P
[18:04] * Technix sticks a microphone near BGA... "speech"
[18:04] * slaad hides.
[18:04] BGA.... so how many other bugs are there?
[18:04] Technix: Sure. But say it is 90% sure. It depends on fixing this llicking thing.
[18:04] sorry I should have been more clear... known bugs
[18:04] slaad: LOL! :)
[18:04] I hear persistence pays off... ;)
[18:04] HotPlasma: We will have to try it out... So far, only a chkbfs bug...
[18:04] And the locking thing.
[18:05] The locking is beingresolved now.
[18:05] chkbfs will probably wait for the next version.
[18:05] yeah Locking is usually something stupid
[18:05] Also, we already have mkbfs working.
[18:05] I remember I had that issue
[18:05] BGA : also, one more question... is it OpenBeFS, or OpenBFS?
[18:05] BGA SWEET!
[18:06] the "BeFS" moniker tends to be used by the *nix folks since there's another filesystem out there from ages ago called BFS
[18:06] Banyan I think
[18:06] * DeadYak checks
[18:06] openBFS" 
 
Want to be a fly on the wall when the news happens on IRC? Hop onto irc.freenode.net and join the #openbeos or #beos channels with your favorite IRC client. Just remember to be polite, ask your questions once (no repeating please), and always respect the @operators. ;)
 
*note: my pc clock is set several hours behind where I live, so that's why Vision displays that time in the log... This event actually occurred sometime around 0000 GMT. *