[Bug 147881] [zfs] [patch] ZFS "sharenfs" doesn't allow different "exports" options for different hosts

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Jun 3 14:41:30 UTC 2019


--- Comment #12 from Richard S. Conto <Richard.Conto at 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.

You are receiving this mail because:
You are the assignee for the bug.

More information about the freebsd-fs mailing list