On 2015-08-07 12:26, carverknut wrote:
> I mean by saying “Yast does not work in mounting NFS” that I expected
> Yast to update /etc/fstab with the NAS routing data (e. g. 192.168.x.x
> and so on) once I entered all the data and make it available after
> startup. But it does not - for reasons I cannot tell or even resolve.
> Now I learn that it is cifs - can that be automatically mounted upon
> startup?
YaST NFS Client module fails because it is not an NFS share, it is a
Samba, aka cifs, share.
There is a yast2-samba-client module, though, but it is called “Windows
domain membership”, so that will not be useful in this case, I’m afraid
> As long as it is convenient for users to access their NAS folders upon
> startup of their machines, I do not care if it is NFS or cifs (but that
> is just my user’s perspective).
Basically, NFS is Unix/Linux style. Samba is Windows style. The crucial
difference is that Samba does not, can not, use Linux attributes
(permissions, ownership) on files. Thus, you can not use that NAS to do
Linux backups.
The line in fstab should be something similar (untested) to
//192.168.1.2/share /NASknut/share cifs defaults,nofail 0 0
If a password is needed, it can go into another file, but I don’t
remember how. Have a read here:
> Samba and Suse: HowTo Set up an openSUSE-Windows Home Office LAN/Network.
The site is not up 24 hours a day, but it explains all the details well.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))