Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
fstat + stat inode support #119
It looks like in the stream wrapper that the values for inodes in
Is that from a limitation, or is that just something that support hasn't been added yet?
The context is that I have a unit-test that needs to behave in a certain way when a file on a disk has been unlinked, and replaced with a file of the same name, but checks the inode values to see if it is the original file. Which is not testable currently using vfsStream as the inodes are always 0, so it appears to be the same file.
I think for most people who are concerned with inodes, the behaviour would be 'correct enough' if
However, if I'm the first person to ask about it, it's probably not worth doing. Or at least not justified by a single person asking about it.
Although skipping file IO in unit tests is a nice idea, getting the vfs stuff to support it correctly might be a non-trivial amount of work.