adbfs
adbfs copied to clipboard
Support writes from Finder on OSX.
Yea, Finder doesn't seem to think it can write, and some other apps (namely Preview). I've had better luck with things that don't try to do a bunch of fancy metadata/versioning stuff (command line, Sublime Text). I think the Finder problem might have to do with resource forks, but adbfs isn't showing any errors, just that Finder opens and closes the ._* files a bunch and occasionally writes to them.
Does this include from a terminal under OS X?
I just updated with a git pull
and then ./install.sh
and after running adbfs-automount
I can't touch foo
, I get the old touch: foo: Operation not permitted
That's a bug. When did you start seeing this? Does it happen on other devices?
On Sat, Apr 2, 2016, 09:28 Julian Frumar [email protected] wrote:
Does this include from a terminal under OS X?
I just updated with a git pull and then ./install.sh and after running adbfs-automount I can't touch foo, I get the old touch: foo: Operation not permitted
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/zach-klippenstein/adbfs/issues/34#issuecomment-204752775
I have just re-tested it with the Genymotion emulator, and the Android emulator and both give the same "Operation not permitted" error.
I removed the src dir in my $GOPATH, then I re-run the install instructions (to fetch the src from GitHub and install.sh), then when i run adbfs-automount
the device mounts OK in my ~/mnt dir. I can then cd
into it and see the list of default sdcard directories, but if I try a mkdir foo
or touch foo.txt
both result in the operation not permitted error.
Anything else I should try? Thanks!
Are you mounting with the --no-readonly
flag?
Thank you for developing this useful tool! I am really looking forward to the 'write from finder' support, so I wonder whether you are still developing this project or not. Please let me know. Thanks!