Date: Thu, 2 Jun 2022 23:30:48 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: Adonis Peralta <donileo@gmail.com> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: NFSv4 on MacOS Monterey Message-ID: <YQBPR0101MB97423EA18C0D8986DAA30462DDDE9@YQBPR0101MB9742.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <C0BD4628-9C6E-4455-B860-521FEA45BF63@gmail.com> References: <5B070ACE-9ECD-4FAA-A975-C77BE87CEFAA@gmail.com> <YQBPR0101MB9742A0A5CACD34C777B2570EDDDE9@YQBPR0101MB9742.CANPRD01.PROD.OUTLOOK.COM> <C0BD4628-9C6E-4455-B860-521FEA45BF63@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Adonis Peralta <donileo@gmail.com> wrote: > Rick Macklem <rmacklem@uoguelph.ca> wrote: > > Yep, as noted above, they aren't supported and will not work. FreeBSD uses the Linux style extended > > attribute model, not the resource fork/subfile one that Mac OSX and Solaris use. > > > > Is this still the case if the shares are on ZFS? Yes. > Is there any info on when or if FreeBSD will get namedattr support? It has been discussed and I have seen no indication that namedattr/ resource forks will ever be implemented. The same appears to be true of Linux. I recall that there were significant issues related to userspace things like archivers, etc. There would also be significant changes needed to the VOP/VFS, since resource forks (or whatever you call them) are really files in a different namespace. rick -- Adonis
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YQBPR0101MB97423EA18C0D8986DAA30462DDDE9>