Bug 4508 - /dev/console and /dev/null have to be created on udev based systems also
Summary: /dev/console and /dev/null have to be created on udev based systems also
Status: RESOLVED WORKSFORME
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: 2011.08
Hardware: PC Linux
: P5 minor
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-22 09:23 UTC by Alexander
Modified: 2011-11-22 09:29 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander 2011-11-22 09:23:14 UTC 
Now buildroot have two device tables - device_table.txt used in static and dynamic /dev variants, and device_table_dev.txt, that is used only in static.

But devices /dev/console and /dev/null have to be static created for both types of /dev filesystem.
So, probably, it would be good to move /dev/null and /dev/console definition from device_table_dev.txt to device_table.txt?
Comment 1 Thomas Petazzoni 2011-11-22 09:29:26 UTC 
No. Our udev and mdev support relies on the devtmpfs filesystem to be enabled in the kernel and mounted at boot time by the kernel. Buildroot ensures that this is the case for kernels that it builds (see the following code in linux/linux.mk), but if you build your kernel outside of Buildroot, it is up to you to enable those options as well.

        $(if $(BR2_ROOTFS_DEVICE_CREATION_STATIC),,
                $(call KCONFIG_ENABLE_OPT,CONFIG_DEVTMPFS,$(@D)/.config)
                $(call KCONFIG_ENABLE_OPT,CONFIG_DEVTMPFS_MOUNT,$(@D)/.config))

So you must enabled CONFIG_DEVTMPFS and CONFIG_DEVTMPFS_MOUNT in your kernel.