behavior of exists/isFile/isDir on mounts

[backbone87]

Several use cases... example structure:

• / <- LocalAdapter A
• /fileA1 <- file of A
• /dirA1 <- dir of A
• /dirA2 <- dir of A, LocalAdapter B mounted onto
• /dirA2/fileB1 <- file of B
• /dirA2/dirB1 <- dir of B
• /dirV1 <- LocalAdapter C mounted onto, does not exists in A
• /dirV1/fileC1 <- file of C
• /dirV1/dirC1 <- dir of C

What happens when:

• exists dirV1 / isDirectory dirV1

[tristanlins]

A mount point like dirV1 exists in virtual environment and per definition is it a directory.

[backbone87]

Ok, and if we change the structure to:

• /dirV1 <- does not exists in A
• /dirV1/dirV2 <- LocalAdapter C mounted onto, does not exists in A
• /dirV1/dirV2/fileC1 <- file of C
• /dirV1/dirV2/dirC1 <- dir of C

What should exists dirV1 and exists dirV1/dirV2 say now?

[tristanlins]

you cannot move parent paths of mounts because it would be an implicit move of a mount that is forbidden ;-)

sry, this is wrong. You can rename the parents in a unix fs, the mount path changes with moves.

[backbone87]

this is not about moving, that is the setup according to a possible configuration

[tristanlins]

exists say true on both, because dirV1 must be exists "virtual" otherwise you can't iterate over it ;-)

[backbone87]

What happens on touch('dirV1/fileA5')

[tristanlins]

I would implicit make a mkdir to dirV1, because we suggest that it is a real directory, even it is only virtual by the mount.