From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] missing /proc in romfs
Date: Wed, 7 May 2008 10:49:35 +1000 [thread overview]
Message-ID: <20080507004934.GA26439@cloud.net.au> (raw)
In-Reply-To: <4820A5F0.7030205@ripnet.com>
On Tue, May 06, 2008 at 02:39:44PM -0400, Mike Sander wrote:
> According to the buildroot docs the filesystem skeleton is available in
> /generic/target_skeleton. The target_skeleton does include /proc.
> After I do a make, the project_build_arm/uclibc/root/ does NOT contain a
> /proc filesystem. I'm not sure if other bits are missing.
Correct, /proc will be an empty directory. The target system will mount
procfs onto /proc during boot, usually from /etc/rc or a similar script.
> I have studied the output of the make process and have not been able to
> see where the basic filesystem is created. I can see where specific
> bits are added to /etc /lib. Could someone be so kind as to describe
> the initial steps in building the root filesystem (and where
> target_skeleton fits in). A brief list of the makefiles (and make
> targets) would be helpful.
The main Makefile has a target $(PROJECT_BUILD_DIR)/.root which copies
the target_skeleton into the project_build_$arch/$project/root
directory, and then other packages are installed into that some root.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
prev parent reply other threads:[~2008-05-07 0:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 18:39 [Buildroot] missing /proc in romfs Mike Sander
2008-05-07 0:49 ` Hamish Moffatt [this message]
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=20080507004934.GA26439@cloud.net.au \
--to=hamish@cloud.net.au \
--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.