jeans/motioneyeos
jeans/motioneyeos
1
0
Fork 0
mirror of https://github.com/motioneye-project/motioneyeos.git synced 2025-07-28 13:46:32 +00:00
Code Issues Packages Projects Releases Wiki Activity

manual: update /dev management section.

Browse Source 
This patch updates the /dev management section in the manual with information
about eudev, which replaces udev.

Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr>
Acked-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Acked-by: Samuel Martin <s.martin49@gmail.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This commit is contained in:
eric.le.bihan.dev@free.fr 2014-02-07 14:21:35 +01:00 committed by Peter Korsgaard
parent 2c66e4429d
commit 46dde29fbb
1 changed files with 11 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
docs/manual/configure.txt
View File

@ -216,7 +216,7 @@ x86_64 target, you have to generate a cross-compilation toolchain with
Buildroot or crosstool-NG. Buildroot or crosstool-NG.
If you want to generate a custom toolchain for your project, that can If you want to generate a custom toolchain for your project, that can
be used as an external toolchain in Buildroot, our recommandation is be used as an external toolchain in Buildroot, our recommendation is
definitely to build it with http://crosstool-ng.org[crosstool-NG]. We definitely to build it with http://crosstool-ng.org[crosstool-NG]. We
recommend to build the toolchain separately from Buildroot, and then recommend to build the toolchain separately from Buildroot, and then
_import_ it in Buildroot using the external toolchain backend. _import_ it in Buildroot using the external toolchain backend.
@ -310,22 +310,24 @@ different solutions to handle the +/dev+ directory :
about +mdev+ and the syntax of its configuration file, see about +mdev+ and the syntax of its configuration file, see
http://git.busybox.net/busybox/tree/docs/mdev.txt. http://git.busybox.net/busybox/tree/docs/mdev.txt.
* The fourth solution is *Dynamic using udev*. This method also * The fourth solution is *Dynamic using eudev*. This method also
relies on the _devtmpfs_ virtual filesystem detailed above, but relies on the _devtmpfs_ virtual filesystem detailed above, but
adds the +udev+ userspace daemon on top of it. +udev+ is a daemon 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 that runs in the background, and gets called by the kernel when a
device gets added or removed from the system. It is a more device gets added or removed from the system. It is a more
heavyweight solution than +mdev+, but provides higher flexibility heavyweight solution than +mdev+, but provides higher flexibility.
and is sometimes mandatory for some system components (systemd for +eudev+ is a standalone version of +udev+, the original userspace
example). +udev+ is the mechanism used in most desktop Linux daemon used in most desktop Linux distributions, which is now part
distributions. For more details about +udev+, see of Systemd. For more details, see http://en.wikipedia.org/wiki/Udev.
http://en.wikipedia.org/wiki/Udev.
The Buildroot developers recommandation is to start with the *Dynamic The Buildroot developers recommendation is to start with the *Dynamic
using devtmpfs only* solution, until you have the need for userspace using devtmpfs only* solution, until you have the need for userspace
to be notified when devices are added/removed, or if firmwares are 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 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+.
init system init system
~~~~~~~~~~~ ~~~~~~~~~~~