diff options
author | Saul Wold <sgw@linux.intel.com> | 2013-06-25 15:14:48 -0700 |
---|---|---|
committer | Saul Wold <sgw@linux.intel.com> | 2013-06-27 09:55:58 -0700 |
commit | d3616f31617830cac9375e8f4aa33e344ac554ed (patch) | |
tree | b18f45a91cc16c92fb1c7d048abcd08931888331 /scripts/contrib/python/generate-manifest-2.7.py | |
parent | 6e1b17f19411ed897c53ae0ef41a2d2972a9c113 (diff) | |
download | openembedded-core-d3616f31617830cac9375e8f4aa33e344ac554ed.tar.gz openembedded-core-d3616f31617830cac9375e8f4aa33e344ac554ed.tar.bz2 openembedded-core-d3616f31617830cac9375e8f4aa33e344ac554ed.zip |
systemd: Ensure that we mount devtmpfs
Since systemd also used tmpfs we should make a similar patch for
the systemd-udev script
Fix for bug: https://bugzilla.yoctoproject.org/show_bug.cgi?id=4632
Since udev 172, the 'mknod' logic was removed from udev. Yocto Dylan
is now using udev 182. This means /dev is now required to be a
devtmpfs filesystem (maintained by the kernel). If the root
filesystem is a ramdisk, the kernel's auto-mount of /dev doesn't
activate since there is no rootfs to actually mount... The bug causes
an unusable system as /dev doesn't contain even basic nodes required
to even get a login prompt.
The Yocto udev/init script mounts tmpfs if it does not detect tmpfs
or devtmpfs mounted at /dev. This appears to be outdated logic that
is no longer correct. I believe the Yocto udev init script should be
checking and mounting only 'devtmpfs' on dev.
Signed-off-by: Alex Olson <alex.olson+yocto@gmail.com>
[YOCTO #4632]
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Diffstat (limited to 'scripts/contrib/python/generate-manifest-2.7.py')
0 files changed, 0 insertions, 0 deletions