https://bugzilla.novell.com/show_bug.cgi?id=760209 https://bugzilla.novell.com/show_bug.cgi?id=760209#c0 Summary: yast2-nfs-server needs revision to match upstream changes to NFSv4 export Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: nfbrown@suse.com QAContact: jsrain@suse.com Found By: Development Blocker: --- Upstream nfs-utils has significantly changed the way that filesystems are exported using NFSv4. It is now much simpler. The old way still works so there is no urgency, but it would be good if future releases discouraged the old way. In the old way, one export must have the 'fsid=0' option. It is then the 'root' that is exported via NFSv4. Other filesystems which are not under that root can be exported below that root by using bind=/some/path. In the new way, fsid=0 is not need and all exported filesystems appear via NFSv4 exactly as you would expect. fsid=0 is still allowed and if it is present, the old way is used. So I would suggest: - don't make fsid=0 a default option when NFSv4 is requested - don't describe the bind= option in the help message - don't make a special case of bind= in the UI. ie. don't display the "Bindmount targets" column. I think we should probably remove "Enable NFSv4" as an option too, and make it always enabled -- 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.