Xuanwo commented on issue #3411: URL: https://github.com/apache/incubator-opendal/issues/3411#issuecomment-1803672616
> * `fuser::Filesystem` provides full functional callbacks for `fuser`, which calls fs manipulation functions from an abstraction layer and utility functions to manipulate inode/path. > * the implementation of the layer can be provided in a lib (maybe `opendal-fs-bridge`? also for the future ACL<->fs permission mapping); > * inode and path name maintenance could be in another lib `opendal-fs-util`. I feel like we are going to far by adding too much crates. How about starting with the simplest setup: a project called `ofs` under `bin` which produces a binary. We can decide whether or not to split it in the future. > 2\. the future ACL<->fs permission mapping); Personally, I don't care about this feature. Since most storage backend don't respect this. We can expect that users always mount fs as `allow_others`. And I can also imagine that users use `ofs` just for data reading and writing like `mountpoint-s3`. However, this is the design details. We can discuss about this in the future. > I had the concern that DalFs was like a toy project and relied too much on `fuser`. That's OK. We don't need to put too much burden on ourselves for a project that just started. We can improve this part later on. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
