All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] chown to root does not work
Date: Fri, 19 Jan 2007 17:33:13 +0100	[thread overview]
Message-ID: <20070119163313.GA17320@aon.at> (raw)
In-Reply-To: <200701191612.12016.thilo@riessner.de>

On Fri, Jan 19, 2007 at 04:12:09PM +0100, Thilo Riessner wrote:
>Am Freitag, 19. Januar 2007 14:35 schrieb Goetz Bock:
>> On Fri, Jan 19 '07 at 13:31, Thilo Riessner wrote:
>> > In the docs is mentioned, that one doesn't need to be root to build a
>> > root filesystem. But when building the filesystem as a normal user, chown
>> > is not able to change owner to root in the target filesystem. Is there a
>> > solution of the problem, that I don't see?

Who does call chown in there? Which package?
Please show me the logs around the alleged call to chown that is
failing.

>>
>> Use fakeroot. Than the cpio/tar/... root images are owned by root.
>I don't know fakeroot. What is it? A programme, an option of buildroot? How do 
>I have to use it?
>Thanks for your help so far.

  reply	other threads:[~2007-01-19 16:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-19 12:31 [Buildroot] chown to root does not work Thilo Riessner
2007-01-19 13:35 ` Goetz Bock
2007-01-19 15:12   ` Thilo Riessner
2007-01-19 16:33     ` Bernhard Fischer [this message]
2007-01-22 18:16       ` Thilo Riessner
2007-01-22 20:02         ` Bernhard Fischer
2007-01-22 20:30           ` Bernhard Fischer
2007-01-23 17:23             ` Thilo Riessner
2007-01-23 23:05               ` Bernhard Fischer
2007-01-23 22:20             ` Claus Klein
2007-01-23 23:14               ` Bernhard Fischer
2007-01-24  6:14                 ` Claus Klein

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=20070119163313.GA17320@aon.at \
    --to=rep.dot.nop@gmail.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 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.