Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Souf Oued <souf_oued@yahoo.fr>
To: buildroot@busybox.net
Subject: [Buildroot] There are not device files in dev/ when I extract tarball image as root. bug?
Date: Sun, 18 Apr 2010 23:19:47 +0200	[thread overview]
Message-ID: <4BCB7773.9010003@yahoo.fr> (raw)
In-Reply-To: <87ljckcxcx.fsf@macbook.be.48ers.dk>

Le 18/04/2010 22:35, Peter Korsgaard a ?crit :
>>>>>> "Thomas" == Thomas Petazzoni<thomas.petazzoni@free-electrons.com>  writes:
>
>   >>  Does it must mknod manually?
>
>   Thomas>  No, it's a regression that I caused by the recent filesystem code
>   Thomas>  cleanup. I'm working on the fix. As an ugly workaround you can add:
>
>   Thomas>  TARGET_DEVICE_TABLE=target/device/generic/device_table.txt
>
>   Thomas>  at the beginning of fs/common.mk.
>
> And with the new BR2_ROOTFS_DEVICE_TABLE kconfig setting Thomas added.
>
Simply put :
include fs/common.mk (line 321)
after
include target/Makefile.in  (line 324)

in buildroot/Makefile

Thanks.

      reply	other threads:[~2010-04-18 21:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-17  1:20 [Buildroot] There are not device files in dev/ when I extract tarball image as root. bug? 徐开
2010-04-17  3:39 ` Thomas Petazzoni
2010-04-18 20:35   ` Peter Korsgaard
2010-04-18 21:19     ` Souf Oued [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=4BCB7773.9010003@yahoo.fr \
    --to=souf_oued@yahoo.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