I got an Zyxel Nas326 which i filled with 2 still good 6TB drives i had access to. Now, i have several questions in regard. And, in advance my excuses for being so ingeniuous …
I can access the server either using smb or afp (from what i read, afp should be better as for speed). nfs should work too, but does not (probably because of problems with username & password which are not transmitted - and i do not see how to set up in the configuration software on the nas a handshake by ip addresses).
Anyway in Thunar all that (afp and cifs) works fine, but Thunar laments too about nfs. But, since I’d like to be able to access the net volumes by ranger as well - and i would like to have an automated access i think i should set up one (or more, if more volumes should be mounted) line in fstab.
But how? I found this instruction: host_name:/share_name /Volumes/mount_name url automounted,url==afp://user_name:password@host_name/share_name 0 0
What would be the correct format of host_name? The plain text or the ip?
And what would be the correct format of url? http://ip.adress or afp://ip.adress?
When i handish mount the drive i get an error msg that afpfsd is not configured to be run by uid=1000 (which would be me, but runs at 0, which i presume is root (?) ). How can i change the config of afpfsd consequentely, if so … ? I experienced, by chance that setting group=wheel me gives access anyway.
And, at least, a question regarding fuse: I realize there is no group fuse on my machine (although fuse is installed) - should there be such group and who should be in that group? So eventually i could add the mounted drive to fuse to have access to it …
Note that the host_name must resolve to the actual IP address of the host computer. You could modify /etc/hosts to add the host_name to it if the host_name cannot be resolved by the DNS server.
So the ip address is fine, as is the hostname assuming it can be resolved.
It may be that it only works on a mac, since that guide is for a mac. You can try, but have a live USB handy just in case.
Because mount is trying to mount the device you gave it and group=wheel is not a valid path or device.
I don’t know about the rest. Maybe these will help, if you haven’t already read them. I’d try NFS again, but if that isn’t working then samba might be the path of least resistance.
Never even heard of afp until this post, so not sure about mount_afp, but it’s not mount so it may not be compatible. What makes you think this is right?
It’s missing the filesystem type, otherwise it at least looks a bit like an fstab entry, whether it is or not . Did you try:
If it’s not that then I’d just move on to samba or back to nfs, due to the lack of info on afp. Unless someone else has more info, or running the command on login is acceptable.
I can’t find anything about fstab entries for afp and linux, the only things I can find are about using linux as a fileserver for a mac.
At least you have a command that works, you can always run it at login or whatever.
In theory, i think it wouldn’t be state of the art, but … at least i could write a script and execute it automatically at the end of my startup programs, i think …
Then a, related, question: is it useful to have a group fuse (where i belong to, obviously and which rights should that group have?
I haven’t used a remote filesystem in a few years and when I did it was nfs, don’t remember using fuse. I have used fuse once or twice at some point, but I currently don’t have a fuse group not sure I ever have.
EDIT:
About the only recent thing I can find about a fuse group is this.
Users are allowed to use fuse if they could read and write to /dev/fuse ie they are in group fuse on debian system. Starting with Debian 8 (Jessie) this group is not required anymore because /dev/fuse is world-writeable.
My system seems to agree that a fuse group is no longer needed.
$ ls -l /dev/fuse
crw-rw-rw- 1 root root 10, 229 Dec 24 15:32 /dev/fuse
That is actually not adding you as the user, but instead executing that command as that user, see sudo(8):
-u user, --user=user
Run the command as a user other than the default target user (usually root). The user may be either a user
name or a numeric user-ID (UID) prefixed with the ‘#’ character (e.g., #0 for UID 0). When running commands as
a UID, many shells require that the ‘#’ be escaped with a backslash (‘\’). Some security policies may restrict
UIDs to those listed in the password database. The sudoers policy allows UIDs that are not in the password
database as long as the targetpw option is not set. Other security policies may not support this.
There seems to be an netatalkAUR package in the works which might help…
. Did you try: