Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> Yes. While we are at it, do I have to define my own diskfs_init_dir, too?
> It increases nlink for . and .., and checks the number of allowed links for
> the parent directory for the latter. (if yes, this should probably be added
> to the info doc on diskfs_link_max).
Yes.
> About the inode stuff: Currently I settled on a virtual inode
> concept which decouples the inode numbering from the directory
> location. This is easier on the reader of the code (no weirdness),
> simpler to implement and it should be possible to use a common
> implementation for all inodeless filesystems there to come.
That sounds cool. However, inode numbers need to be stable for NFS,
or you need to implement your own file_getfh and fsys_getfile.
Thomas
