Systemd/extras/run_directory
Kay Sievers 1aa1e24848 replace libsysfs
We never used any of the libsysfs convenience features. Here we replace
it completely with 300 lines of code, which are much simpler and a bit
faster cause udev(d) does not open any syfs file for a simple event which
does not need any parent device information.

Signed-off-by: Kay Sievers <kay.sievers@suse.de>
2006-01-09 21:18:00 +01:00
..
dev.d remove example rules and put the dev.d stuff into the run_directory folder 2005-08-09 20:11:26 +02:00
Makefile replace libsysfs 2006-01-09 21:18:00 +01:00
README trivial text cleanups 2005-08-09 22:11:44 +02:00
RFC-dev.d remove example rules and put the dev.d stuff into the run_directory folder 2005-08-09 20:11:26 +02:00
run_directory.c replace libsysfs 2006-01-09 21:18:00 +01:00
run_directory.h Fixed udev_run_devd to run the /etc/dev.d/DEVNAME/ files too 2005-07-14 15:19:37 -07:00
udev_run_devd.c replace libsysfs 2006-01-09 21:18:00 +01:00
udev_run_hotplugd.c replace libsysfs 2006-01-09 21:18:00 +01:00

Use these binaries only if you need backward compatibility with
older udev versions. The use of /etc/dev.d/ is no longer recommended.
Use explicit udev rules with RUN keys to hook into the processing.

  /etc/dev.d/ + /etc/hotplug.d/ directory multiplexing is completely
  removed from udev itself and must be emulated by calling small
  helper binaries provided by these helpers:
      make EXTRAS=extras/run_directory/
    will build udev_run_devd and udev_run_hotplugd, which can be called
    from a rule if needed:
      RUN+="/sbin/udev_run_hotplugd"
    The recommended way to handle this is to convert all the calls from
    the directories to explicit udev rules and get completely rid of the
    multiplexing. (To catch a ttyUSB event, you now no longer need to
    fork and exit 300 tty script instances on bootup you are not interested
    in, it is just one rule that matches exactly that single device.)