Date: Mon, 24 May 2021 13:16:10 +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-oto9ZEQHEe@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 #20 from Richard S. Conto <Richard.Conto@gmail.com> --- I've abandoned it. My use-case no longer applies. Given the limits expressed in this discussion - a technical limitation on t= he length of ZFS property value lengths, and a political reluctance to allow self-documenting configurations, if I were to re-implement this, I'd do this entirely outside of ZFS as it'd be a FreeBSD-only solution anyway. A generic "share export builder" tool, like "rebuilder" for firewall rules, that would implement a common configuration format and produce appropriate configurations for FreeBSD, Linux, Solaris - for NFS, NFS4, CIFS, et. al. c= omes to mind - and would likely be a dead-end. The classic "exports" format is crufty. The inability to share filesystems/paths that contain whitespace was tolerable in a teletype focus= ed world 40 years ago. Continuing to support that old format is not the same t= hing as supporting ONLY that old format, but the later is where we're at. --=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-oto9ZEQHEe>