Re: nfs exports by local dns

On Fri, Dec 5, 2025 at 7:17 AM Rick Macklem <[email protected]> wrote:
>
> On Fri, Dec 5, 2025 at 6:06 AM Gerrit Kühn <[email protected]> wrote:
> >
> > Am Fri, 5 Dec 2025 13:35:17 +0000
> > schrieb void <[email protected]>:
> >
> > > the short form hostname seems to work well in the zfs sharenfs line
> > > but I've not needed to try yet to split it over long lines with
> > > backslash
> >
> > Thanks for sharing your experience.
> > Your lines above remind me of the long-standing issue that there is no
> > easy way to have sharenfs produce multiple lines in the exports file. Upon
> > reviewing the situation, I found that there has been a patch for this
> > (already in summer 2024): https://reviews.freebsd.org/D45814
> > It has even been merged to the openzfs
> > repo: https://github.com/openzfs/zfs/pull/16338
> >
> > Is there some easy way to find out where a particular patch like this went
> > in the FreeBSD git repo (i.e., which release might have it)? I thought
> > this should be easy to tell, but so far I was not able to find out how.
> > It looks like it did not make it into 14.3 (but maybe 15.0?).
> Just look at the history for the same file in FreeBSD's repo.
> (In this case: sys/contrib/openzfs/lib/libshare/os/freebsd/nfs.c)
> You have to click on the commit (in this case ce4dcb9) to see the
> list of OpenZFS commits pulled.
>
> It was committed to main in Aug. 10, 2024 as a part of ce4dcb9
One thing I will note is that it did take me a looonnggg time to get
around to doing this.

If anyone has a patch for ZFS, they can set it up as a pull request
for OpenZFS on github. They do not need to be a FreeBSD committer.
(Once reviewed/pulled by OpenZFS it will find its way into FreeBSD.)

rick

>
> rick
>
> >
> >
> > cu
> >   Gerrit