Adonis Peralta wrote:
> Rick Macklem 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 ZF
>> mountd_enable="YES"
> Since you have specified nfsv4_server_only, mountd will be configured
> correctly (using the -R),
> so this line is not needed (although I don't thing it will cause trouble).
Got it.
>> My configuration is as follows:
>>
>> SERVER CONFIGURATION
>>
>> OS: FreeBSD 13.1
>>
Rick Macklem wrote:
> Adonis Peralta wrote:
[stuff snipped]
> > OS: FreeBSD 13.1
[more stuff snipped]
> > RESULTS
> >
> > What I see when I connect via finder is the following:
> >
> > 1. I am able to read/write to the shares since /etc/exports contains the
> > -mapall line, yet inspecting a pa
Adonis Peralta wrote:
> I have some NFSv4 (sec=sys) shares on FreeBSD 13.1 which I'm trying to
> connect correctly with MacOS 12.4 > Monterey.
> I got the basics down but don't think I have permissions and extended
> attributes working correctly.
Well, here are a few comments. Note that I haven'
I have some NFSv4 (sec=sys) shares on FreeBSD 13.1 which I'm trying to connect
correctly with MacOS 12.4 Monterey.
I got the basics down but don't think I have permissions and extended
attributes working correctly.
My configuration is as follows:
SERVER CONFIGURATION
OS: FreeBSD 13.1
===
/etc
