Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ficheux <pierre.ficheux@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] mdev problem in 2011.08 ?
Date: Sun, 18 Sep 2011 18:44:59 +0200	[thread overview]
Message-ID: <4E76200B.40608@openwide.fr> (raw)
In-Reply-To: <20110918162842.02150727@skate>

Le 18/09/11 16:28, Thomas Petazzoni a ?crit :
> Hello Pierre,
> 
> Le Sun, 18 Sep 2011 15:01:51 +0200,
> Pierre Ficheux <pierre.ficheux@openwide.fr> a ?crit :
> 
>> May be I'm wrong but it seems there is a problem when using mdev for
>> /dev management:
> 
> For our mdev and udev support, we assume that the kernel is compiled
> with CONFIG_DEVTMPFS and CONFIG_DEVTMPFS_MOUNT. 

Kernel config looks fine:

$ grep DEVTMPFS output/build/linux-2.6.34.5/.config
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y

But I still have:

Freeing unused kernel memory: 328k freed
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 logging: OK
Starting mdev...
mdev: /sys/class: No such file or directory

I test with QEMU + rootfs.cpio, does it matter?

-- 
Pierre FICHEUX -/- CTO OW/OWI, France -\- pierre.ficheux at openwide.fr
                                         http://ingenierie.openwide.fr
                                         http://www.ficheux.org
I would love to change the world, but they won't give me the source code

  reply	other threads:[~2011-09-18 16:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-18 13:01 [Buildroot] mdev problem in 2011.08 ? Pierre Ficheux
2011-09-18 14:28 ` Thomas Petazzoni
2011-09-18 16:44   ` Pierre Ficheux [this message]
2011-09-18 17:14     ` Thomas Petazzoni

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=4E76200B.40608@openwide.fr \
    --to=pierre.ficheux@openwide.fr \
    --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