From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] root permissions issue (reformatted)
Date: Wed, 14 Dec 2011 16:01:49 -0300 [thread overview]
Message-ID: <4EE8F29D.7040706@zacarias.com.ar> (raw)
In-Reply-To: <32975350.post@talk.nabble.com>
On 12/14/11 15:58, dan robinson wrote:
> I have an NFS mounted root. The directory, on the NFS server, does not have
> write permissions for 'other'. I am not able to create a file when I run
> the command, 'touch one'. On the NFS server side, I run 'chmod o+w' and
> that is shown in the second 'ls' command. I can create a file.
>
> If I 'su' to default, I can create files in that user's directory.
>
> Note that the file, 'one', is owned by 65534. I have included the
> /etc/passwd file. This is -2 in 16 bits. Noteworthy?
>
> I ran the 'id' command.
> # id
> uid=0(root) gid=0(root) groups=0(root),10(wheel)
>
> Ideas?
>
> --dan robinson
Yes, "man exports" and look at the root_squash and no_root_squash option
descriptions.
Regards.
next prev parent reply other threads:[~2011-12-14 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 18:58 [Buildroot] root permissions issue (reformatted) dan robinson
2011-12-14 19:01 ` Gustavo Zacarias [this message]
2011-12-14 19:07 ` dan robinson
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=4EE8F29D.7040706@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.