From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Improper device nodes createdinsideproject_build_arm/uclibc/root/dev/
Date: Thu, 24 Apr 2008 11:31:59 +0200 [thread overview]
Message-ID: <87wsmna99s.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <004201c8a593$e3796b20$080514ac@atmel.com> (Ulf Samuelsson's message of "Wed\, 23 Apr 2008 20\:33\:47 +0200")
>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
Hi,
>> Sure, but where to stop? I think most if not all disk based needs are
>> covered by the existing tar/ext2/ext3 support.
Ulf> I am just talking about a configuration option which will
Ulf> write a file system generated using the existing options
Ulf> to the SD-Card card.
Ulf> config BR2_WRITE_SD_CARD
Ulf> string "Write to SD-Card in the /mnt area"
Ulf> default "sdcard"
Why special case SD cards? it can be any block device you want. What
about permissions?
I still think it's silly - What is next, add stuff to fire up a
terminal emulator (with config options for port and baudrate) and
upload file to bootloader?
>> Not in a current project, no - But I have (or rather CF cards, but
>> that's the same). What's the problem with the existing ext2 support?
Ulf> It creates the file in $(BINARIES_DIR) and not on the SD-card.
Ulf> It would make sense to allow creating a CF-card as well.
What's the difference between CF and SD card support? The big
difference between putting stuff in BINARIES_DIR and on some block
device is permissions. You can do everything in buildroot without root
permissions, let's not change that.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-04-24 9:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 6:14 [Buildroot] Improper device nodes created inside project_build_arm/uclibc/root/dev/ Hebbar
2008-04-21 14:07 ` Hamish Moffatt
2008-04-22 0:12 ` Hebbar
2008-04-22 0:50 ` Hamish Moffatt
2008-04-22 1:58 ` [Buildroot] Improper device nodes created insideproject_build_arm/uclibc/root/dev/ Gururaja Hebbar K R
2008-04-22 1:56 ` Hamish Moffatt
2008-04-22 7:54 ` Peter Korsgaard
2008-04-22 7:14 ` [Buildroot] Improper device nodes created inside project_build_arm/uclibc/root/dev/ Peter Korsgaard
2008-04-22 9:59 ` Hamish Moffatt
2008-04-22 16:40 ` [Buildroot] Improper device nodes createdinside project_build_arm/uclibc/root/dev/ Ulf Samuelsson
2008-04-22 18:24 ` Peter Korsgaard
2008-04-22 18:47 ` Ulf Samuelsson
2008-04-22 20:52 ` Peter Korsgaard
2008-04-23 0:45 ` Thiago A. Corrêa
2008-04-23 17:03 ` [Buildroot] Improper device nodes createdinsideproject_build_arm/uclibc/root/dev/ Ulf Samuelsson
2008-04-23 18:09 ` Peter Korsgaard
2008-04-23 18:33 ` Ulf Samuelsson
2008-04-24 9:31 ` Peter Korsgaard [this message]
2008-04-25 15:00 ` Thiago A. Corrêa
2008-04-22 7:12 ` [Buildroot] Improper device nodes created inside project_build_arm/uclibc/root/dev/ Peter Korsgaard
2008-04-23 5:45 ` Hebbar
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=87wsmna99s.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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