Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] system/device_table.txt: add /dev/null entry
Date: Thu, 27 Nov 2014 22:14:45 +0200	[thread overview]
Message-ID: <20141127201445.GD4690@tarshish> (raw)
In-Reply-To: <20141127203720.10997803@free-electrons.com>

Hi Thomas,

On Thu, Nov 27, 2014 at 08:37:20PM +0100, Thomas Petazzoni wrote:
> On Thu, 27 Nov 2014 08:44:36 +0200, Baruch Siach wrote:
> > /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
> > ...
> > 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
> > 
> > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> > ---
> >  system/device_table.txt | 1 +
> >  1 file changed, 1 insertion(+)
> 
> So, in the end, my proposal would be to drop this patch, and instead
> have a patch that fixes the cpio code to not create this
> useless /dev/console device when cpio is not enabled. We have not
> supported udev/mdev without devtmpfs since a long time, I don't really
> see the point of bringing this back, as 2.6.32 is now very old and most
> people have the possibility of moving to a 2.6.32+ kernel.
> 
> Baruch, do you agree with this proposal?

Supporting a non devtmpfs with mdev only requires creating /dev/null and 
/dev/console statically. I think this is a small price to pay for an 
out-of-the-box working build. Anyway, I don't feel strongly about it. I can 
easily work around the problem with a custom device table file, at least as 
long as I haven't rebuilt the kernel.

By the way, the kernel that comes with this board IS 2.6.32, and we have just 
now started development based on the SoC on the board.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2014-11-27 20:14 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
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 [this message]
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=20141127201445.GD4690@tarshish \
    --to=baruch@tkos.co.il \
    --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