public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] NFS mounts and uid/gid/user names
Date: Sat, 25 Aug 2012 08:44:44 +0100	[thread overview]
Message-ID: <20120825084444.5ba01fe5@hactar.digimed.co.uk> (raw)
In-Reply-To: <20120824225641.GB3510@solfire>

[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]

On Sat, 25 Aug 2012 00:56:41 +0200, meino.cramer@gmx.de wrote:

> In /etc/exports on the PC I entered this:
> /tmp/NFS 192.168.178.25(async,rw,no_subtree_check)
> 
> When setting chmod 700 /tmp/NFS, chown root:root /tmp/NFS
> on the server side (PC) I cannot write to the directory
> as root on the client side (single board computer).
> On both sides root is 0:0.
> 
> When setting chmod 777 /tmp/NFS on the server side, I am able to write
> at the client side to the that directory, bit listing that files shows
> me that they become owned by nobody:nobody which is
> nobody:x:65534:65534:nobody:/nonexistent:/bin/sh on the server side.

Where did you get the no_subtree_check options from? If you'd read it in
the man page you'd have seen that you also need no_root_squash. Without
this option, the root user on the client is mapped to a non-root user on
the server.


-- 
Neil Bothwick

WinErr 079: Mouse not found - A mouse driver has not been installed.
            Please click the left mouse button to continue.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-08-25  7:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24 22:56 [gentoo-user] NFS mounts and uid/gid/user names meino.cramer
2012-08-25  7:44 ` Neil Bothwick [this message]
2012-08-25  7:45 ` Alex Schuster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120825084444.5ba01fe5@hactar.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox