How about this: The pointer handle represents a generic filesystem node just for the purposes of navigating the client's local image of the hierarchy, but *_open() returns a numerical handle that is used in vfs_read(), vfs_write(), vfs_truncate(), etc. I.e. the functions operating on file's contents would be simple IPC wrappers, and the fat stuff is used just for navigating the file tree.
This sounds perfectly reasonable to me.
Although, I can't figure out what would be a proper name and prefix for the "generic fs node" type.
Some suggestions for the prefix (inspired by different contexts, I don't know what is more fitting): dirent, dentry, junction, namespace, vfs_namespace, vfs_node, vfs_tree
M.D. _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
