On 2020-04-05 08:24, Ed Greshko wrote:
FWIW, I just enabled afp on my synology NAS and installed the fuse-afp on my linux system.
Then.....
[egreshko@f31k ~]$ mount_afpafp://myusername:mypasswd@192.168.1.142/aux apple
The afpfs daemon does not appear to be running for uid 1026, let me start it for you
Mounting 192.168.1.142 from aux on apple
Mounting of volume aux of server nas succeeded
[egreshko@f31k ~]$ ls apple
backups linux-releases qemu-images
[egreshko@f31k ~]$ touch apple/x
[egreshko@f31k ~]$ rm apple/x
demonstrates I have rw access to that directory on the server.
°
I'm back at this again and see the following result:
bobg]# mount_afp afp://my_mycloud_username:12345678@192.168.2.202/aux
/mnt/test
Mounting 192.168.2.202 from aux on /mnt/test
Login error: Authentication failed
Those user credentials work with the WD Mycloud browser page and provide
access to the files, but I suspect not directly from the mycloud device,
images must be downloaded and viewed, in my case with gthumb. It can
take a minute or two to view one jpeg.
I am told that when an image is stored to the iCloud server it is
removed from the iPhone camera leaving only a low resolution
"thumbnail." Viewing a a high resolution image requires a connection to
the iCloud. That explains some of the high bandwidth usage that I see,
if true, what an awful scheme!
Anyway I want to see what is actually store on the WD Mycloud device, it
should be the complete high resolution image file ...
The question now is what's wrong with mount_afp authorization? I think I
made /mnt/test/ accessible with chmod 777 /mnt/test/.
--
Bob Goodwin - Zuni, Virginia,
Fedora Linux-31 XFCE
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
