shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2024-10-31 07:51:08 +03:00
Code
eba25b20ce
systemd-stable/extras/run_directory
History
Marco d'Itri 77914dfeda run_directory: fix typo in "make install"
2005-09-16 21:05:15 +02: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 run_directory: fix typo in "make install" 2005-09-16 21:05:15 +02: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 allow logging of all output from executed tools 2005-08-11 17:32:59 +02: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 Really commit the udev_run_devd changes... 2005-07-14 15:24:59 -07:00
udev_run_hotplugd.c Really commit the udev_run_devd changes... 2005-07-14 15:24:59 -07:00

README 

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.)