BVolume method to ask which characters a filesystem considers invalid
|Reported by:||jonas.kirilla||Owned by:||nobody|
Copying filesets to non-BFS filesystems in Tracker often stalls on filenames having characters not allowed on the target filesystem. It would be nice if Tracker's pre-copy analysis could be extended to also check for filenames that would be invalid on the target volume, and warn about these before starting the copy process.
One could provide a method
status_t BVolume::InvalidCharacters(BString& string)
which would populate the given string with characters considered invalid by the volume's filesystem, using a syscall to ask the filesystem for its set of invalid characters.
It's not unthinkable that some filesystems have more complex naming rules, but perhaps this API is sufficient. It is advisory rather than authoritative/final.