https://bugzilla.novell.com/show_bug.cgi?id=819515
https://bugzilla.novell.com/show_bug.cgi?id=819515#c5
--- Comment #5 from Scott Couston
So it seems you really issue is with Yast. Consequently I am reassigning this to yast developers.
Main issues seem to be: - autofs is much better for mounting NFS filesystems than /etc/fstab. It should be possible and easy to configure NFS mounts to use autofs - if /etc/fstab is to be used, the "bg" option should be available so that missing servers don't cause the boot to hang.
There might be others that I missed.
Thank you so much for ageing to commit manpower to this problem. This bug goes back to 10.3 and this is the first commitment of resources and for that, I thank you. I dont think any NETWORK drive should be written to /etc/fstab. Auto fs should sit and wait for NFS drives to become present and then not present. If a network drive becomes available, auto mount, the when not available auto dismount and so forth. I think the NFS Server needs to advertise relentlessly and if NFS clients become online the drive is auto mounted. The ability to run application over a NFS drive is perfectly wonderful right now. I run Evolution and all locally held data is on an NFS drive. It makes backing up data from a single source very easy to manage. Its a small data server concept that can be hugely taken advantage of Most of Yast no-loner or has never worked, take Security Centre and Hardening in Yast. under Miscellaneous change the file permission to 'secure' or 'paranoid' and the PC dead and destroyed and not able to be backed out of. Again, thank you for the commitment of resources in this one small area -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.