[openbeos] Re: A note to file system writers

"François Revol" <revol@xxxxxxx> wrote:
> I thought this bug was located in Tracker... wasn't there a 
> similar illed behaviour before in R5 and it was fixed in OT ?
> or was it just a side effect that got fixed ? now I wonder why 
> it doesn't trigger in R5.

That was a different bug :)
I don't remember what exactly was the cause, though, but this fixed it:
http://cvs.sourceforge.net/viewcvs.py/opentracker/opentracker/tracker/NavMenu.cpp?r1=1.3&r2=1.4

> I'll go update NFS since it has that problem in Zeta.
> Though I'm pretty sure there is ..
> do I have to fill in the correct block dev id and inodes for 
> the parent or does the vfs correct it by itself ?

The VFS should correct these values automatically, since you don't even 
know about your exact mount point (or don't have to, at least) :)

Bye,
   Axel.

Other related posts: