From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Improper device nodes createdinside project_build_arm/uclibc/root/dev/
Date: Tue, 22 Apr 2008 18:40:53 +0200 [thread overview]
Message-ID: <040301c8a49d$c1408170$050514ac@atmel.com> (raw)
In-Reply-To: 20080422095909.GA31643@cloud.net.au
> On Tue, Apr 22, 2008 at 09:14:16AM +0200, Peter Korsgaard wrote:
>> >>>>> "Hamish" == Hamish Moffatt <hamish@cloud.net.au> writes:
>>
>> Hi,
>>
>> >> If this is what it is suppose to do, then how to mount the same for NFS
>> >> boot.
>>
>> Hamish> You could mount a generated image file somewhere via the loopback
>> Hamish> device. Then you would have the devices that are in the image. ext2
>> Hamish> would be a good choice. Do you want to write back to the root or not?
>>
>> Hamish> Alternatively you could add a new target output format for NFS root.
>>
>> We already have that - tarball creation.
>
> Good point. So, Hebbar: just use the tarball target, and extract it somewhere
> (as root) for use by your target system. Don't mount the
> buildroot/project_build.../.../root directory directly as it won't
> contain the real devices.
>
Maybe we should have a configuration item allowing this to happen
automatically using "sudo".
I guess, in that case, we should have another
configuration item (defaulting to no) which enables use of "sudo".
If we decide to do this, then I think that we need to be pretty
careful so we do not allow to untar in the host "/" directory or
other directories which will destroy the host installation.
Maybe we should only allow it to be in "~/.buildroot/<project>/root".
Opinions?
Best Regards
Ulf Samuelsson ulf at atmel.com
Atmel Nordic AB
Mail: Box 2033, 174 02 Sundbyberg, Sweden
Visit: Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22 Fax +46 (8) 441 54 29
GSM +46 (706) 22 44 57
next prev parent reply other threads:[~2008-04-22 16:40 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 ` Ulf Samuelsson [this message]
2008-04-22 18:24 ` [Buildroot] Improper device nodes createdinside project_build_arm/uclibc/root/dev/ 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
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='040301c8a49d$c1408170$050514ac@atmel.com' \
--to=ulf.samuelsson@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox