James Carlson <[email protected]> writes:
> Harry Putnam writes:
>> That kind of mount using this command:
>>
>> mount -F nfs reader:/pub /pub
>>
>> results in a mounted filesystem that cannot be written to by users.
>
> Things (from a confessed non-expert) to check:
>
> - does the server export the file system as read-write to this
> client?
> - does the server implement some sort of user-based security?
Just for the record, yes and maybe. The maybe is on suspicion that
the option added by the bug report ("sec=sys") makes it work at
all.. appears to be somekind of security realted thing, though doesn't
really appear to be user invoked especially.
Not to prolong the discussion here but just for your information: The
export line from linux server now looks like (wrapped for mail):
/pub \
192.168.0.0/22(rw,insecure,sec=sys,no_root_squash,subtree_check)
I have a hunch `insecure' and `sec-sys' might run at cross purposes
but decided to leave it alone since at least I can now mount the
share.
Thanks James for your kind patience and helpful answers. I'll finally
take the hint and move this discussion as you suggested.
And one more thing for the record... this group doesn't discuss `nfs'
and apparently `cifs' is on a different list too. What is its focus?
_______________________________________________
networking-discuss mailing list
[email protected]
