Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] cannot log to my build root
Date: Tue, 14 Dec 2010 17:00:15 +0100	[thread overview]
Message-ID: <20101214170015.23afdb41@surf> (raw)
In-Reply-To: <AANLkTik3m_kFJjxqo-Y3XS0J+AjbhPfXQ3CiSXvVOs6n@mail.gmail.com>

On Tue, 14 Dec 2010 17:56:06 +0200
Diego Iastrubni <diegoiast@gmail.com> wrote:

> And now it works. The problem is that shadow was not readable from the
> remote NFS.  Now I wait for the correct fix for this problem.

Ah, that's because your NFS directory is incorrectly exported. You
should use the no_root_squash option.

Otherwise, root accesses from the remote machine are made on the NFS
server as the nobody user, which obviously, can't access the
rootfs/etc/shadow file.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-12-14 16:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 13:06 [Buildroot] cannot log to my build root Diego Iastrubni
2010-12-14 13:25 ` Thomas Petazzoni
2010-12-14 13:39   ` Diego Iastrubni
2010-12-14 14:05     ` Thomas Petazzoni
2010-12-14 14:38       ` Diego Iastrubni
2010-12-14 14:42         ` Thomas Petazzoni
2010-12-14 14:54           ` Diego Iastrubni
2010-12-14 15:05             ` Thomas Petazzoni
2010-12-14 15:28               ` Diego Iastrubni
2010-12-14 15:37                 ` Thomas Petazzoni
2010-12-14 15:56                   ` Diego Iastrubni
2010-12-14 16:00                     ` Thomas Petazzoni [this message]
2010-12-14 15:50                 ` William Wagner
2010-12-14 16:00                   ` Thomas Petazzoni

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=20101214170015.23afdb41@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox