From: Peter Korsgaard <jacmet@uclibc.org>
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 22:35:42 +0200 [thread overview]
Message-ID: <87ljckcxcx.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20100417053913.528536ef@surf> (Thomas Petazzoni's message of "Sat, 17 Apr 2010 05:39:13 +0200")
>>>>> "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.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-04-18 20:35 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 [this message]
2010-04-18 21:19 ` Souf Oued
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=87ljckcxcx.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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