Bug 4125 - udev_182 recipe's init allows use of tmpfs but udev-182 only works with devtmpfs
Summary: udev_182 recipe's init allows use of tmpfs but udev-182 only works with devtmpfs
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.4
Hardware: x86 arm
: Medium normal
Target Milestone: 1.4 M6
Assignee: Saul Wold
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-03-26 19:48 UTC by Wayne Warren
Modified: 2013-04-15 23:43 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

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 Wayne Warren 2013-03-26 19:48:25 UTC 
I am working on a building a new distro based on the metadata provided by yocto/poky for a custom ARM product for which we are using our own custom kernel.

We are currently working off of poky git tag 1.4_M4.final.

The problem I am seeing at the moment is that the udev init script will attempt to mount /dev using 'tmpfs' if 'devtmpfs' is not available when in fact (according to someone I spoke with on #udev) udev-182 requires the use of devtmpfs. 

I understand that Yocto typically expects to build its own kernel with a particular configuration that probably already includes devtmpfs, but it seems like the init script out to fail with a useful message anyway if devtmpfs is not available.