Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] proc not mouning
Date: Thu, 24 Mar 2011 19:58:30 +0100	[thread overview]
Message-ID: <20110324195830.5a30d30c@surf> (raw)
In-Reply-To: <1D6034426110564DA0DEA9EE9793B3835817742BC0@NBE-MBX01.americas.swk.pri>

Hello,

On Wed, 23 Mar 2011 16:35:16 -0400
"Heyendal, Carl" <CHeyendal@stanleyworks.com> wrote:

> I was originally generating the root filesystem as a cpio archive and
> using that to populate my SD card. Later on, as a build optimization,
> I disabled generating rootfs.cpio at the top level Buildroot
> menuconfig. Instead I started copying 'output/target/*' over to my SD
> card. That's when the trouble began I guess. I switched back to using
> rootfs.cpio to populate the SD card and I no longer have the
> problem. :-)

From the Buildroot documentation at
http://buildroot.org/downloads/buildroot.html :
 
 target/ which contains almost the complete root filesystem for the
 target: everything needed is present except the device files in /dev/
 (Buildroot can't create them because Buildroot doesn't run as root and
 doesn't want to run as root). Therefore, this directory should not be
 used on your target. Instead, you should use one of the images built in
 the images/ directory. If you need an extracted image of the root
 filesystem for booting over NFS, then use the tarball image generated
 in images/ and extract it as root.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2011-03-24 18:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-22 21:39 [Buildroot] Compiling Apache Michael Burghart
2011-03-22 14:59 ` Eric BENARD
     [not found]   ` <4D88BD19.7070901@michaelburghart.de>
     [not found]     ` <4D88C6B3.5010103@free.fr>
2011-03-22 16:07       ` Michael Burghart
2011-03-22 19:33       ` Michael Burghart
2011-03-22 19:55         ` Baruch Siach
2011-03-22 20:00           ` Michael Burghart
2011-03-22 20:03             ` Baruch Siach
2011-03-22 20:21               ` Michael Burghart
2011-03-23  6:12                 ` Michael Burghart
2011-03-23 17:16                   ` Baruch Siach
2011-03-23 19:02                     ` [Buildroot] proc not mouning Heyendal, Carl
2011-03-23 19:27                       ` bruce bushby
2011-03-23 19:32                       ` ANDY KENNEDY
2011-03-23 19:35                         ` Heyendal, Carl
2011-03-23 19:43                           ` ANDY KENNEDY
2011-03-23 19:46                             ` Heyendal, Carl
2011-03-23 19:36                         ` bruce bushby
2011-03-23 20:35                       ` Heyendal, Carl
2011-03-23 21:14                         ` ANDY KENNEDY
2011-03-24 18:58                         ` Thomas Petazzoni [this message]
2011-03-24 19:04                           ` Heyendal, Carl
2011-10-21 16:29                             ` vbr vbr
2011-10-28 12:50                               ` Peter Korsgaard
2011-03-24  6:42                     ` [Buildroot] Compiling Apache Michael Burghart
2011-03-22 19:35       ` Michael Burghart

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=20110324195830.5a30d30c@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