Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulfs@dof.se>
To: buildroot@busybox.net
Subject: [Buildroot] chown 0 <file> fails while generating root file system
Date: Sun, 14 Jan 2007 19:41:15 +0100	[thread overview]
Message-ID: <009b01c7380f$a56568e0$01c4af0a@atmel.com> (raw)

I am using buildroot-2006-11-01 with my own modifications.
When generating the root file system file (JFFS2/EXT2)
at the end, a file "install.sh" is called in build_arm/sudo-<ver>
which will chown some files to be owned by root.

This fails, since I am running as a normal user
so all files are owned by the user make'ing the buildroot.

I upgraded the operating system to OpenSuse 10.2 and this
generated error messages of type: (translated from Swedish)

chown: changing owner of "<file>": Operation not allowed

Is this a known problem?
I have not seen this error message when using OpenSuse 10.1 
on the same buildroot sources.

If known, has it been fixed in later version?


Best Regards,
Ulf Samuelsson
ulf at atmel.com
GSM:  +46 (706) 22 44 57
Tel:     +46  (8) 441 54 22
Fax:     +46 (8) 441 54 29
Mail: Box 2033  174 02 Sundbyberg
Visit: Kavalleriv?gen 24
          174 58 Sundbyberg'
Sweden
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20070114/52e35936/attachment.htm 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: buildroot_err.txt
Url: http://busybox.net/lists/buildroot/attachments/20070114/52e35936/attachment.txt 

             reply	other threads:[~2007-01-14 18:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-14 18:41 Ulf Samuelsson [this message]
2007-01-15 16:45 ` [Buildroot] chown 0 <file> fails while generating root file system Bernhard Fischer

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='009b01c7380f$a56568e0$01c4af0a@atmel.com' \
    --to=ulfs@dof.se \
    --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