-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello FreeBSD users out there.
My last build and update of /usr/doc was end of May 2017; since then any
attempt building
the doc from /usr/doc failed on 12-CURRENT to 12-STABLE and now on 13-CURRENT.
I believe all the required ports (following
Hello Matthew,
I appreciate the long write up, as someone who still uses FreeBSD ZFS on my NAS
box and knowing some of the history with ZFS on *Solaris, etc. Something like
this was bound to happen with post the Oracle buyout.
> On Dec 18, 2018, at 10:49 PM, Matthew Macy wrote:
>
> The
The sources for FreeBSD's ZFS support are currently taken directly
from Illumos with local ifdefs to support the peculiarities of FreeBSD
where the Solaris Portability Layer (SPL) shims fall short. FreeBSD
has regularly pulled changes from Illumos and tried to push back any
bug fixes and new
On Tue, Dec 18, 2018 at 5:07 PM Rick Macklem wrote:
> The change to make the FreeBSD NFSv4 server use vfs.nfsd.nfs_privport is
> trivial
> and I think being compatible with Linux is important (I see it as the defacto
> standard NFS implementation these days).
>
> What do others think I should
It was my understanding that the NFSv4 working group believed that the
requirement
for the NFSv4 client to use a priviledged port# (< 1024) should not exist.
As such, I coded the server to ignore the vfs.nfsd.nfs_privport sysctl and
allow the
mount for NFSv4.
PR#234106 has reported this as a
