Date: Sat, 6 Dec 2025 07:09:01 -0800 From: Rick Macklem <rick.macklem@gmail.com> To: Ronald Klop <ronald-lists@klop.ws> Cc: =?UTF-8?B?R2Vycml0IEvDvGhu?= <gerrit.kuehn@aei.mpg.de>, void <void@f-m.fm>, freebsd-fs@freebsd.org Subject: Re: nfs exports by local dns Message-ID: <CAM5tNy5P5=VjXKRXaQC8zDXFkQV3FrgG61KTae94roAOkotF8Q@mail.gmail.com> In-Reply-To: <254762252.11873.1765003943072@localhost> References: <CAM5tNy5XzAHMCFuS1UJ1Gjke0EsaqnY6W6e-LLfSdS8AiEHOnQ@mail.gmail.com> <254762252.11873.1765003943072@localhost>
index | next in thread | previous in thread | raw e-mail
On Fri, Dec 5, 2025 at 10:52 PM Ronald Klop <ronald-lists@klop.ws> wrote: > > Rick, > > Would you like to close the review? As this is committed already. Done. It normally happens automagically, but since the commit was to OpenZFS.. rick > > https://reviews.freebsd.org/D45814 > > > Regards, > > Ronald > > > Van: Rick Macklem <rick.macklem@gmail.com> > Datum: 5 december 2025 16:23 > Aan: "Gerrit Kühn" <gerrit.kuehn@aei.mpg.de> > CC: void <void@f-m.fm>, freebsd-fs@freebsd.org > Onderwerp: Re: nfs exports by local dns > > On Fri, Dec 5, 2025 at 7:17AM Rick Macklem wrote: > > > > On Fri, Dec 5, 2025 at 6:06AM Gerrit Kühn wrote: > > > > > > Am Fri, 5 Dec 2025 13:35:17 +0000 > > > schrieb void : > > > > > > > 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 > > ________________________________ > > > >help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAM5tNy5P5=VjXKRXaQC8zDXFkQV3FrgG61KTae94roAOkotF8Q>
