@ChrisH
Quote:
Of course it's up to the filesystem how it interprets that. I thought that a request for the parent of root returned root, at least on FFS. I've just checked and only ram-handler (and my webdav-handler, more by accident than design) treats the parent of root as root, smbfs redirects to SYS: (I'd consider this a bug) and FFS and SFS2 error it as an invalid path.
I'm not blaming the filesystems btw, I find path handling is often broken on lazy ports.
If you want a workaround you could create a soft-link in RAM: pointing to the volume you actually want to scan, and scan the link instead. That should work.