Bug 760209

Summary:	yast2-nfs-server needs revision to match upstream changes to NFSv4 export
Product:	[openSUSE] openSUSE 12.2	Reporter:	Neil Brown <nfbrown>
Component:	YaST2	Assignee:	Martin Vidner <mvidner>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Enhancement
Priority:	P5 - None	CC:	mfilka
Version:	Factory
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Neil Brown 2012-05-02 01:16:50 UTC

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

Comment 1 Kun Kun Zhang 2012-05-02 06:44:12 UTC

HI,could you please help to have a look at this?Thank you:)

Comment 2 Martin Vidner 2014-05-21 12:52:45 UTC

Michal implemented this as https://fate.suse.com/315589 , thanks!