On Wed, Nov 29, 2006 at 12:26:22AM -0800, Brad Boyer wrote: > For a more extreme case, hfs and hfsplus don't even have a separation > between directory entries and inode information. The code creates this > separation synthetically to match the expectations of the kernel. During > a readdir(), the full catalog record is loaded from disk, but all that > is used is the information passed back to the filldir callback. The only > thing that would be needed to return extra information would be code to > copy information from the internal structure to whatever the system call > used to return data to the program. In this case you can infact already instanciate inodes froms readdir. Take a look at the NFS code. - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
