Matthew Dillon wrote:
Log: Detect the case where rename()ing over a file that has been unlinked but is still open was reporting an inode hash collision instead of a fatal error. msdosfs uses the position of the directory entry within the directory to identify the inode and a new file cannot be created if the removed file is still held open by a program.
But isn't that only an implementation issue? As long as you keep the "first sector" and "size" information in memory, you can drop the directory entry. I might be wrong, however. cheers simon -- Serve - BSD +++ RENT this banner advert +++ ASCII Ribbon /"\ Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
