Date: Mon, 03 Jun 2019 14:41:27 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 147881] [zfs] [patch] ZFS "sharenfs" doesn't allow different "exports" options for different hosts Message-ID: <bug-147881-3630-GTPTSbBThJ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-147881-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-147881-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D147881 --- Comment #12 from Richard S. Conto <Richard.Conto@gmail.com> --- I considered re-writing my patch to use a FreeBSD specific attribute for my syntax (or an expanded one that would allow white-space in the pathnames - = but that would have involved modifying how the "exportfs" command parsed .../exports files.) But frankly, this was a sort of proof-of-concept that addressed a need for adapting to the FreeBSD .../exports file format that wasn't being addressed. And the FreeBSD project didn't care enough. Of course there are compatibility issues with the Solaris version of ZFS - because "sharenfs" is implemented as a hack to begin with. Pushing the administration of ZFS mount points into a hand-administered /etc/exports files ignores scalability issues. The FreeBSD .../exports file format doesn't scale well and is an ugly hack itself. A proper fix to this should include revisiting whether that file format should be extended or supplemented. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-147881-3630-GTPTSbBThJ>