From: Sven Neumann <neumann@teufel.de>
To: buildroot@busybox.net
Subject: [Buildroot] Default target file system permissions
Date: Sat, 02 Nov 2013 19:30:58 +0100 [thread overview]
Message-ID: <1383417058.5894.5.camel@bender> (raw)
In-Reply-To: <20131102110658.779bbcb5@skate>
Hi,
On Sat, 2013-11-02 at 11:06 +0100, Thomas Petazzoni wrote:
> > Here's how the root folder on our target file-system looks like:
> >
> > drwxr-xr-x 20 root root 4096 Dec 7 1999 .
> > drwxr-xr-x 20 root root 4096 Dec 7 1999 ..
> > drwx------ 2 root root 4096 Dec 7 1999 bin
> > drwxr-xr-x 2 root root 4096 Nov 30 1999 boot
> > drwxr-xr-x 5 root root 4096 Dec 30 1999 data
> > drwxr-xr-x 10 root root 12600 Dec 7 1999 dev
> > drwxr-xr-x 15 root root 4096 Dec 7 1999 etc
> > drwx------ 3 root root 4096 Dec 7 1999 home
> > drwx------ 4 root root 4096 Dec 7 1999 lib
> > lrwxrwxrwx 1 root root 11 Oct 31 20:26 linuxrc ->
> > bin/busybox
> > drwx------ 2 root root 4096 Dec 7 1999 media
> > drwx------ 2 root root 4096 Dec 7 1999 mnt
> > drwx------ 2 root root 4096 Dec 7 1999 opt
> > dr-xr-xr-x 62 root root 0 Dec 7 1999 proc
> > drwx------ 2 root root 4096 Oct 31 22:09 root
> > lrwxrwxrwx 1 root root 3 Oct 31 18:39 run -> tmp
> > drwx------ 2 root root 4096 Dec 7 1999 sbin
> > dr-xr-xr-x 11 root root 0 Dec 7 1999 sys
> > drwxrwxrwt 12 root root 800 Oct 31 21:51 tmp
> > drwx------ 7 root root 4096 Dec 7 1999 usr
> > drwxr-xr-x 7 root root 4096 Dec 7 1999 var
>
> Interesting, because here I don't have the same behavior:
>
> drwxrwxr-x 2 root root 1420 nov. 1 13:24 bin
> drwxr-xr-x 3 root root 100 nov. 1 13:24 dev
> drwxr-xr-x 5 root root 500 nov. 1 13:24 etc
> drwxrwxr-x 4 root root 80 nov. 1 13:24 home
> drwxrwxr-x 2 root root 540 nov. 1 13:24 lib
> lrwxrwxrwx 1 root root 3 nov. 1 13:22 lib32 -> lib
> lrwxrwxrwx 1 root root 11 nov. 1 13:24 linuxrc -> bin/busybox
> drwxrwxr-x 2 root root 40 oct. 27 12:37 media
> drwxrwxr-x 2 root root 40 oct. 27 12:37 mnt
> drwxrwxr-x 2 root root 40 oct. 27 12:37 opt
> drwxrwxr-x 2 root root 40 oct. 27 12:37 proc
> drwx------ 2 root root 100 oct. 27 12:37 root
> lrwxrwxrwx 1 root root 3 oct. 27 12:37 run -> tmp
> drwxrwxr-x 2 root root 940 nov. 1 13:24 sbin
> drwxrwxr-x 2 root root 40 oct. 27 12:37 sys
> drwxrwxrwt 3 root root 60 nov. 1 13:24 tmp
> drwxrwxr-x 6 root root 140 nov. 1 13:24 usr
> drwxrwxr-x 4 root root 220 nov. 1 13:24 var
>
> How are the permissions of the directories/files in system/skeleton/ in
> your Buildroot sources?
OK, that made me think and I've now checked the contents of the
rootfs.tar created by buildroot instead of looking at the deployed
filesystem on the target device. It appears that this is a bug in the
way that we deploy the rootfs and has nothing to do with buildroot. I am
very sorry for bothering you with this. Thanks for your attempt to help,
Regards,
Sven
next prev parent reply other threads:[~2013-11-02 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 8:13 [Buildroot] Default target file system permissions Sven Neumann
2013-11-02 10:06 ` Thomas Petazzoni
2013-11-02 18:30 ` Sven Neumann [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-31 22:42 Sven Neumann
2013-11-02 22:23 ` Arnout Vandecappelle
2013-01-21 4:38 Przemyslaw Wrzos
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=1383417058.5894.5.camel@bender \
--to=neumann@teufel.de \
--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