Hello, I had this on my SuSE machines since SuSE 10.3, always without problems: A NAS acts as NFS server and my SuSE machine as NFS client. I simply create some mount directories and let yast2 do the magic in creating the connection between NAS as NFS server and machine as NFS client. I never touched any NFS config files as it worked out of the box as it should be. Now I changed to SuSE 13.1, did the same as always and it hangs at a certain time when booting. :-(((( After I switch on the NAS, the boot goes on. What is that hickup? I just use the default yast2 settings as with every SuSE before. After deleting the NFS shares in Yast2 there is only one share that appears in df -k I unmount that and the next one appears. I unmount the 2nd and the 3rd appears ->? In previous versions of SuSE "df -k" always showed all NFS shares! In this forum there are other problems with NFS but afaics not this one. Internet is not helpful. https://en.opensuse.org/YaST_NFS_Client says "Boot times increased while waiting for a response from network NFS servers. This was resolved with full systemd which simply bypasses unavailable drives using short timeouts and then connects when drives become available. " Is that broken? Any pointers? Thx -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org