From: Hans-Christian Egtvedt <hcegtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/device/Atmel: atngw100/target_skeleton atngw100/target etc...
Date: Mon, 27 Aug 2007 14:38:51 +0200 [thread overview]
Message-ID: <1188218331.7840.26.camel@localhost.localdomain> (raw)
In-Reply-To: <20070821013441.98D34A610B@busybox.net>
On Mon, 2007-08-20 at 18:34 -0700, ulf at uclibc.org wrote:
> Author: ulf
> Date: 2007-08-20 18:34:40 -0700 (Mon, 20 Aug 2007)
> New Revision: 19596
>
> Log:
> additional skeleton for AVR32
>
> Added:
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/bin/
What is up with all the directories? Is not defining them
in .../<board>/device_table.txt enough? I find it far better defining
them there since the access permissions can be defined as well.
Same for all the directories below.
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/boot/
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/config/
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/dev/
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/home/
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/lib/
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/mnt/
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/opt/
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/root/
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/root/.bash_history
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/root/.bash_logout
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/root/.bash_profile
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/root/.bashrc
What are the needs for these bash-files? I find the default bash
behavior to be ok.
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/sbin/
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/tmp/
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/var/
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/var/cache/
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/var/lib/
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/var/lib/pcmcia/
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/var/lock/
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/var/log/
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/var/pcmcia/
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/var/run/
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/var/spool/
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/var/tmp/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/bin/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/boot/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/config/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/dev/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/home/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/lib/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/mnt/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/opt/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/proc/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/root/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/root/.bash_history
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/root/.bash_logout
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/root/.bash_profile
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/root/.bashrc
Same as previous .bash-files.
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/sbin/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/tmp/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/var/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/var/cache/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/var/lib/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/var/lib/pcmcia/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/var/lock/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/var/log/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/var/pcmcia/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/var/run/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/var/spool/
> trunk/buildroot/target/device/Atmel/atstk1002/target_skeleton/var/tmp/
<cut diff>
--
With kind regards,
Hans-Christian Egtvedt, Applications Engineer
next prev parent reply other threads:[~2007-08-27 12:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 1:34 [Buildroot] svn commit: trunk/buildroot/target/device/Atmel: atngw100/target_skeleton atngw100/target etc ulf at uclibc.org
2007-08-27 12:38 ` Hans-Christian Egtvedt [this message]
2007-08-27 21:15 ` Bernhard Fischer
2007-08-27 21:40 ` [Buildroot] svn commit: trunk/buildroot/target/device/Atmel:atngw100/target_skeleton " Ulf Samuelsson
-- strict thread matches above, loose matches on Subject: below --
2008-10-18 12:47 [Buildroot] svn commit: trunk/buildroot/target/device/Atmel: atngw100/target_skeleton " jacmet at uclibc.org
2008-10-18 13:32 ` Markus Heidelberg
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=1188218331.7840.26.camel@localhost.localdomain \
--to=hcegtvedt@atmel.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.