You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I work a lot with rust-fuse under Android however there is a lot of adjustment to make it work, several reasons for this:
Libfuse is mostley unavailable (mountpoint must be mount from the FUSE device using libc::mount).
FUSE filesystem can only be mounted from a root process.
There is some Android kernel specific FUSE operations that are actually very specific to the FAT emulation layer of Android.
On Android device mountpoint must match the FAT emulation layer.
for theses reasons a native rust mount feature must be written, a remove-all of the libfuse depandancy and some OS specific op code to make it work.
Currently all these features are available into my fork although some rewriting is required to maintain code quality so I wonder if it's worth to start a serious PR for the addition of Android support or these too specific changes and low demand make it should stay in a indepandant fork.
The text was updated successfully, but these errors were encountered:
It's working on vanilla linux but that require root privileges cause we're using libc::mount.
If you are interested here is an implementation of fuse mount for android that also work on most linux link
I work a lot with
rust-fuse
under Android however there is a lot of adjustment to make it work, several reasons for this:libc::mount
).FAT
emulation layer of Android.FAT
emulation layer.for theses reasons a native rust mount feature must be written, a remove-all of the libfuse depandancy and some OS specific op code to make it work.
Currently all these features are available into my fork although some rewriting is required to maintain code quality so I wonder if it's worth to start a serious PR for the addition of Android support or these too specific changes and low demand make it should stay in a indepandant fork.
The text was updated successfully, but these errors were encountered: