From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] Add network scripting folders to fs/skeleton
Date: Tue, 28 Sep 2010 19:40:24 +0200 [thread overview]
Message-ID: <20100928194024.2ccf72e8@surf> (raw)
In-Reply-To: <4C9C55C5.907@visionsystems.de>
On Fri, 24 Sep 2010 09:39:49 +0200
Yegor Yefremov <yegor_sub1@visionsystems.de> wrote:
> Those folders by device_table.txt. If using the dynamic device creation method
> these folders will be missing.
"Those folders are currently created by device_table.txt"...
Ok on the principle, but if those directories are now part of the
skeleton, they should be removed from the device_table.txt file.
However, looking at device_table.txt, I also see that it does a few
things not related to device files :
/dev d 755 0 0 - - - - -
/dev/pts d 755 0 0 - - - - -
/dev/shm d 755 0 0 - - - - -
/tmp d 1777 0 0 - - - - -
/etc d 755 0 0 - - - - -
/home/default d 2755 1000 1000 - - - - -
#<name> <type> <mode> <uid> <gid> <major> <minor> <start> <inc> <count>
/bin/busybox f 4755 0 0 - - - - -
/etc/shadow f 600 0 0 - - - - -
/etc/passwd f 644 0 0 - - - - -
/etc/network/if-up.d d 755 0 0 - - - - -
/etc/network/if-pre-up.d d 755 0 0 - - - - -
/etc/network/if-down.d d 755 0 0 - - - - -
/etc/network/if-post-down.d d 755 0 0 - - - - -
/usr/share/udhcpc/default.script f 755 0 0 - - - - -
For each of those lines, what will replace the usage of the device
table ? For things like proper access rights
for /etc/shadow, /etc/passwd, setuid for Busybox binary, proper flags
for /tmp, maybe we have no other choices than using a device table.
In that case, we could use a split device table :
* One used in all cases
* One used only in the static device case. Buildroot would concatenate
this one to the previous one before doing the root filesystem generation.
Thoughts ?
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-09-28 17:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 7:35 [Buildroot] [PATCH 0/4] /etc/inittab stuff and device creation stuff Yegor Yefremov
[not found] ` <4C9C54FC.4040609@visionsystems.de>
2010-09-24 7:37 ` [Buildroot] [PATCH 2/4] Enable terminal type configuration for /etc/inittab Yegor Yefremov
2010-09-24 7:38 ` [Buildroot] [PATCH 3/4] Create menu entry to select device creation method Yegor Yefremov
2010-09-24 7:39 ` [Buildroot] [PATCH 4/4] Add network scripting folders to fs/skeleton Yegor Yefremov
2010-09-28 17:40 ` Thomas Petazzoni [this message]
2010-11-22 18:47 ` Thomas Petazzoni
2010-09-28 17:35 ` [Buildroot] [PATCH 3/4] Create menu entry to select device creation method Thomas Petazzoni
2010-09-29 12:18 ` Yegor Yefremov
2010-09-30 12:57 ` Yegor Yefremov
2010-11-22 18:47 ` Thomas Petazzoni
2010-09-28 17:28 ` [Buildroot] [PATCH 2/4] Enable terminal type configuration for /etc/inittab Thomas Petazzoni
2010-09-29 8:31 ` Yegor Yefremov
2010-09-27 8:53 ` [Buildroot] [PATCH 1/4] Added new menu item to specify a custom port " Yegor Yefremov
2010-09-28 17:26 ` Thomas Petazzoni
2010-09-29 8:36 ` Yegor Yefremov
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=20100928194024.2ccf72e8@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