-
Notifications
You must be signed in to change notification settings - Fork 7.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TW#12280] VFS: Unable to map the whole file system tree using "/" #135
Comments
You have no options to set base path in your code and use relative paths? |
I imagine this is related to the fact the VFS does not support nested mount points, and therefore would break e.g. the |
I can implement nested mount points if there are some use cases for that. |
i just filed #158 which is related (feel free to dedup) - need to be able to take over the entire vfs. |
Adding a request from @rojer here: we should support paths which don't start with |
If there are no better matches, VFS calls will fall through to this "VFS of last resort". Temporary hack until espressif#135 is fixed.
fwiw, above is my stab at it. |
If there are no better matches, VFS calls will fall through to this "VFS of last resort". Temporary hack until espressif#135 is fixed.
If there are no better matches, VFS calls will fall through to this "VFS of last resort". Temporary hack until espressif#135 is fixed.
If there are no better matches, VFS calls will fall through to this "VFS of last resort". Temporary hack until espressif#135 is fixed.
If there are no better matches, VFS calls will fall through to this "VFS of last resort". Temporary hack until espressif#135 is fixed.
If there are no better matches, VFS calls will fall through to this "VFS of last resort". Temporary hack until espressif#135 is fixed.
If there are no better matches, VFS calls will fall through to this "VFS of last resort". Temporary hack until espressif#135 is fixed.
If there are no better matches, VFS calls will fall through to this "VFS of last resort". Temporary hack until espressif#135 is fixed.
If there are no better matches, VFS calls will fall through to this "VFS of last resort". Temporary hack until espressif#135 is fixed.
If there are no better matches, VFS calls will fall through to this "VFS of last resort". Temporary hack until espressif#135 is fixed.
If there are no better matches, VFS calls will fall through to this "VFS of last resort". Temporary hack until espressif#135 is fixed.
If there are no better matches, VFS calls will fall through to this "VFS of last resort". Temporary hack until espressif#135 is fixed.
If there are no better matches, VFS calls will fall through to this "VFS of last resort". Temporary hack until espressif#135 is fixed.
If there are no better matches, VFS calls will fall through to this "VFS of last resort". Temporary hack until espressif#135 is fixed.
If there are no better matches, VFS calls will fall through to this "VFS of last resort". Temporary hack until espressif#135 is fixed.
If there are no better matches, VFS calls will fall through to this "VFS of last resort". Temporary hack until espressif#135 is fixed.
If there are no better matches, VFS calls will fall through to this "VFS of last resort". Temporary hack until espressif#135 is fixed.
If there are no better matches, VFS calls will fall through to this "VFS of last resort". Temporary hack until espressif#135 is fixed.
Good catch, thanks @rojer. |
I am finding that I am unable to map the whole file system tree as seen by the Posix APIs using
esp_vfs_register()
. It appears that if I try and map "/" that returns an error code. It is as though theesp_vfs_register()
requires that my mount point be subordinate to root ("/"). I am thinking that this may be too restrictive. What if I want to use VFS with just a single type of file system (for examples SPIFFS) then I want all paths to map into the SPIFFS file system not just those from a specific prefix.For example, I want to be able to access
/dir1/file1.txt
and/dir2/file2.txt
through SPIFFS with both files on the same SPIFFS file system.The text was updated successfully, but these errors were encountered: