From d47fd445bd9ade720776f661a4ad7c4b2202d6f0 Mon Sep 17 00:00:00 2001 From: Kay Sievers Date: Tue, 9 Aug 2005 22:11:44 +0200 Subject: [PATCH 1/1] trivial text cleanups Signed-off-by: Kay Sievers --- README | 3 ++- etc/udev/{udev.rules.devfs => udev-devfs.rules} | 3 --- extras/run_directory/README | 6 +++--- 3 files changed, 5 insertions(+), 7 deletions(-) rename etc/udev/{udev.rules.devfs => udev-devfs.rules} (95%) diff --git a/README b/README index 139c6e1a6..5dc1e46c8 100644 --- a/README +++ b/README @@ -85,7 +85,8 @@ To use: If nothing seems to happen, make sure your build worked properly by running the udev-test.pl script as root in the test/ subdirectory of the -udev source tree. +udev source tree. Running udevstart should populate an empty /dev +directory. You may test, if a node is recreated after running udevstart. Development and documentation help is very much appreciated, see the TODO file for a list of things left to be done. diff --git a/etc/udev/udev.rules.devfs b/etc/udev/udev-devfs.rules similarity index 95% rename from etc/udev/udev.rules.devfs rename to etc/udev/udev-devfs.rules index b7b2c4e12..1e71ae1a1 100644 --- a/etc/udev/udev.rules.devfs +++ b/etc/udev/udev-devfs.rules @@ -4,9 +4,6 @@ # it. Use custom rules to name your device or look at the persistent device # naming scheme, which is implemented for disks and add your subsystem. -# There are a number of modifiers that are allowed to be used in some of the -# fields. See the udev man page for a full description of them. - # ide block devices BUS="ide", KERNEL="hd*", PROGRAM="/etc/udev/ide-devfs.sh %k %b %n", NAME="%k", SYMLINK="%c{1} %c{2}" diff --git a/extras/run_directory/README b/extras/run_directory/README index 022c66451..feae2f81b 100644 --- a/extras/run_directory/README +++ b/extras/run_directory/README @@ -1,5 +1,5 @@ Use these binaries only if you need backward compatibility with -older udev versions. The use of /etc/dev.d/ is no longer recommended +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 @@ -12,6 +12,6 @@ Use explicit udev rules with RUN keys to hook into the processing. 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 you are not interested in, it - is just one rule that matches exactly the device.) + 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.) -- 2.30.2