chiark
/
gitweb
/
~ianmdlvl
/
elogind.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
[PATCH] rename namedev_dev to udev_rule
[elogind.git]
/
README
diff --git
a/README
b/README
index 75d642c94238087306e4812a09edc2e049853e37..54cee659a833206953dc521f7ff8f59d4996a673 100644
(file)
--- a/
README
+++ b/
README
@@
-44,16
+44,9
@@
To use:
what udev is doing. This is enabled by default. Note, if you
are building udev against klibc it is recommended that you
disable this option (due to klibc's syslog implementation.)
what udev is doing. This is enabled by default. Note, if you
are building udev against klibc it is recommended that you
disable this option (due to klibc's syslog implementation.)
- USE_DBUS
- if set to 'true', DBUS messages will be sent everytime udev
- creates or removes a device node. This requires that DBUS
- development headers and libraries be present on your system to
- build properly. Default value is 'false'.
USE_SELINUX
USE_SELINUX
- if set to 'true', SELinux support for udev will be built in.
- This requires that SELinux development headers and libraries be
- present on your system to build properly. Default value is
- 'false'.
+ if set to 'true', udev will be built with SELinux support
+ enabled. This is disabled by default.
DEBUG
if set to 'true', debugging messages will be sent to the syslog
as udev is run. Default value is 'false'.
DEBUG
if set to 'true', debugging messages will be sent to the syslog
as udev is run. Default value is 'false'.
@@
-72,7
+65,7
@@
To use:
This will put the udev binary in /sbin, create the /udev and /etc/udev
directories, and place the udev configuration files in /etc/udev. You
This will put the udev binary in /sbin, create the /udev and /etc/udev
directories, and place the udev configuration files in /etc/udev. You
- will probably want to edit the
namedev.*
files to create custom naming
+ will probably want to edit the
*.rules
files to create custom naming
rules. More info on how the config files are set up are contained in
comments in the files, and is located in the documentation.
rules. More info on how the config files are set up are contained in
comments in the files, and is located in the documentation.
@@
-99,7
+92,3
@@
know by sending a message to the linux-hotplug-devel mailing list at:
greg k-h
greg@kroah.com
greg k-h
greg@kroah.com
-
-
-
-