From: Markos Chandras <markos.chandras@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH buildroot] fs/common: Create initial console device
Date: Wed, 31 Oct 2012 09:53:52 +0000 [thread overview]
Message-ID: <1351677232-14959-1-git-send-email-markos.chandras@gmail.com> (raw)
From: Markos Chandras <markos.chandras@imgtec.com>
A /dev/console node must be present in rootfs when the Linux kernel
boots otherwise the kernel will print the following warning:
"Warning: unable to open an initial console"
This is because when we use an initramfs along with devtmpfs, the /dev
directory is not populated at this point. This can cause problems when a
program (e.g ldso with early debugging enabled) opens a standard file
descriptor for read/write before these descriptors are actually created by
the init process later on.
Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>
---
fs/common.mk | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/fs/common.mk b/fs/common.mk
index debf7db..d7383d1 100644
--- a/fs/common.mk
+++ b/fs/common.mk
@@ -55,6 +55,12 @@ endif
echo "$(HOST_DIR)/usr/bin/makedevs -d $(FULL_DEVICE_TABLE) $(TARGET_DIR)" >> $(FAKEROOT_SCRIPT)
endif
echo "$(ROOTFS_$(2)_CMD)" >> $(FAKEROOT_SCRIPT)
+ # create initial console if devtmpfs is used
+ifeq ($(BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_DEVTMPFS),y)
+ echo -e 'pushd $(TARGET_DIR)/dev/ > /dev/null 2>&1' >> $(FAKEROOT_SCRIPT)
+ echo -e '/bin/mknod -m 622 console c 5 1' >> $(FAKEROOT_SCRIPT)
+ echo -e 'popd > /dev/null 2>&1' >> $(FAKEROOT_SCRIPT)
+endif
chmod a+x $(FAKEROOT_SCRIPT)
$(HOST_DIR)/usr/bin/fakeroot -- $(FAKEROOT_SCRIPT)
- at rm -f $(FAKEROOT_SCRIPT) $(FULL_DEVICE_TABLE)
--
1.7.1
next reply other threads:[~2012-10-31 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 9:53 Markos Chandras [this message]
2012-10-31 22:46 ` [Buildroot] [PATCH buildroot] fs/common: Create initial console device Arnout Vandecappelle
2012-11-01 9:22 ` Markos Chandras
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=1351677232-14959-1-git-send-email-markos.chandras@gmail.com \
--to=markos.chandras@gmail.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