[Buildroot] There are not device files in dev/ when I extract tarball image as root. bug?

[Buildroot] There are not device files in dev/ when I extract tarball image as root. bug?

[徐开]

Hi,

I am trying to boot my board over NFS, but show some stuff like "not found
/dev/ttySAC0".

I found this words on buildroot's website:

target/ which contains *almost* the root filesystem for the target:
everything needed is present except the device files in /dev/ (Buildroot
can't create them because Buildroot doesn't run as root and does not want to
run as root). Therefore, this directory *should not be used on your target*.
Instead, you should use one of the images built in the images/ directory. If
you need an extracted image of the root filesystem for booting over NFS,
then use the tarball image generated in images/ and extract it as root.

And I followed it, but I did not get device files except this:

$ ls /tftpboot/rootfs/dev/ -l
??? 1
lrwxrwxrwx 1 root root   10 2010-04-17 00:02 log -> ../tmp/log
drwxr-xr-x 2 root root 1024 2010-04-17 00:02 pts

Does it must mknod manually?


-- 
Aaron Xu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100417/42227483/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config
Type: application/octet-stream
Size: 19468 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100417/42227483/attachment-0001.obj>

[Buildroot] There are not device files in dev/ when I extract tarball image as root. bug?

[Thomas Petazzoni]

On Sat, 17 Apr 2010 09:20:12 +0800
?? <greatsnows@gmail.com> wrote:

> And I followed it, but I did not get device files except this:
> 
> $ ls /tftpboot/rootfs/dev/ -l
> ??? 1
> lrwxrwxrwx 1 root root   10 2010-04-17 00:02 log -> ../tmp/log
> drwxr-xr-x 2 root root 1024 2010-04-17 00:02 pts
> 
> Does it must mknod manually?

No, it's a regression that I caused by the recent filesystem code
cleanup. I'm working on the fix. As an ugly workaround you can add:

TARGET_DEVICE_TABLE=target/device/generic/device_table.txt

at the beginning of fs/common.mk.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] There are not device files in dev/ when I extract tarball image as root. bug?

[Peter Korsgaard]

>>>>> "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

[Buildroot] There are not device files in dev/ when I extract tarball image as root. bug?

[Souf Oued]

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.