system: clarify /dev management using devtmpfs + {mdev, eudev}
PATCH 1/1 system: clarify /dev management using devtmpfs + {mdev, eudev}
The "Dynamic using mdev" and "Dynamic using eudev" /dev management methods are using devtmpfs, just like "Dynamic using devtmpfs only", on top of which they add either mdev or eudev. But their names might suggest they use mdev only or eudev only.
Clarify their descriptions by adding "devtmpfs +" to make it unambiguous.
--- docs/manual/configure.txt | 7 ++++--- system/Config.in | 4 ++-- 2 files changed, 6 insertions(+), 5 deletions(-)
docs/manual/configure.txt +4 -3
@@ -295,7 +295,7 @@ different solutions to handle the +/dev+ directory : responsibility to enable those two options (if you fail to do so, your Buildroot system will not boot). - * The third solution is *Dynamic using mdev*. This method also relies + * The third solution is *Dynamic using devtmpfs + mdev*. This method also relies on the _devtmpfs_ virtual filesystem detailed above (so the requirement to have +CONFIG_DEVTMPFS+ and +CONFIG_DEVTMPFS_MOUNT+ enabled in the kernel configuration still apply), but adds the
@@ -314,7 +314,7 @@ different solutions to handle the +/dev+ directory : about +mdev+ and the syntax of its configuration file, see http://git.busybox.net/busybox/tree/docs/mdev.txt. - * The fourth solution is *Dynamic using eudev*. This method also + * The fourth solution is *Dynamic using devtmpfs + eudev*. This method also relies on the _devtmpfs_ virtual filesystem detailed above, but adds the +eudev+ userspace daemon on top of it. +eudev+ is a daemon that runs in the background, and gets called by the kernel when a
@@ -327,7 +327,8 @@ different solutions to handle the +/dev+ directory : The Buildroot developers recommendation is to start with the *Dynamic using devtmpfs only* solution, until you have the need for userspace to be notified when devices are added/removed, or if firmwares are -needed, in which case *Dynamic using mdev* is usually a good solution. +needed, in which case *Dynamic using devtmpfs + mdev* is usually a +good solution. Note that if +systemd+ is chosen as init system, /dev management will be performed by the +udev+ program provided by +systemd+.
system/Config.in +2 -2
@@ -110,11 +110,11 @@ config BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_DEVTMPFS bool "Dynamic using devtmpfs only" config BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV - bool "Dynamic using mdev" + bool "Dynamic using devtmpfs + mdev" select BR2_PACKAGE_BUSYBOX config BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV - bool "Dynamic using eudev" + bool "Dynamic using devtmpfs + eudev" depends on BR2_USE_WCHAR depends on !BR2_STATIC_LIBS depends on BR2_USE_MMU # eudev
Signature · 1 line
1.9.1
PATCH 1/1 system: clarify /dev management using devtmpfs + {mdev, eudev}
Dear Luca Ceresoli,
Quoted 8 lines · Luca Ceresoli
The "Dynamic using mdev" and "Dynamic using eudev" /dev management methods are using devtmpfs, just like "Dynamic using devtmpfs only", on top of which they add either mdev or eudev. But their names might suggest they use mdev only or eudev only.
Clarify their descriptions by adding "devtmpfs +" to make it unambiguous.
Quoted 6 lines
Signed-off-by Luca Ceresoli <[email protected]>--- docs/manual/configure.txt | 7 ++++--- system/Config.in | 4 ++-- 2 files changed, 6 insertions(+), 5 deletions(-)
Applied after rewrapping the manual text (even if it indeed makes the diff a lot less readable), thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com