From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] system/device_table.txt: add /dev/null entry
Date: Thu, 27 Nov 2014 08:56:40 +0100 [thread overview]
Message-ID: <87fvd5oz47.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <0a2f80f7ceb3272bf534f85fbf5030df36cae191.1417070676.git.baruch@tkos.co.il> (Baruch Siach's message of "Thu, 27 Nov 2014 08:44:36 +0200")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> /dev/null is the "console" for system startup commands listed in the default
> /etc/inittab. These commands fail when /dev/null isn't there. This breaks
> BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV, as /proc and /sys are not mounted when
> mdev runs, causing the following errors:
> can't open /dev/null: No such file or directory
> can't open /dev/null: No such file or directory
> can't open /dev/null: No such file or directory
> can't open /dev/null: No such file or directory
> can't open /dev/null: No such file or directory
> can't open /dev/null: No such file or directory
> ...
Hmm, is this on a kernel without devtmpfs? Devtmpfs is expected to be
used with mdev (and we automatically enable it if you build a kernel
with BR).
> Starting mdev...
> /etc/init.d/S10mdev: line 19: can't create /proc/sys/kernel/hotplug: nonexistent directory
> mdev: /sys/class: No such file or directory
So you don't have /proc and /sys? Is this also a custom rootfs skeleton
/ inittab? With the default one we do a mount -a before running /etc/init.d/rcS.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-11-27 7:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 6:44 [Buildroot] [PATCH] system/device_table.txt: add /dev/null entry Baruch Siach
2014-11-27 7:56 ` Peter Korsgaard [this message]
2014-11-27 8:12 ` Baruch Siach
2014-11-27 9:01 ` Peter Korsgaard
2014-11-27 10:15 ` Baruch Siach
2014-11-27 10:24 ` Peter Korsgaard
2014-11-27 10:35 ` Baruch Siach
2014-11-27 10:39 ` Peter Korsgaard
2014-11-27 19:37 ` Thomas Petazzoni
2014-11-27 20:14 ` Baruch Siach
2014-11-27 21:57 ` Peter Korsgaard
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=87fvd5oz47.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 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.