prepare for new HAL udevdb dump

[elogind.git] / README

diff --git a/README b/README
index 139c6e1a6ff00e77052a0e9b4bd6093b799ee25e..9891c696d374c95765dabc307dbb37db57bc106c 100644 (file)
--- a/README
+++ b/README
@@ -60,11 +60,18 @@ To use:
                This is used if USE_KLIBC=true to find the kernel include
                directory that klibc needs to build against.  This must be set
                if you are not building udev while running a 2.6 kernel.
                This is used if USE_KLIBC=true to find the kernel include
                directory that klibc needs to build against.  This must be set
                if you are not building udev while running a 2.6 kernel.

+       EXTRAS
+               if set, will build the "extra" helper programs as specified
+               as listed (see below for an example.)

 
       So, if you want to build udev using klibc with debugging messages, you
       would do:
        make USE_KLIBC=true DEBUG=true
 
 
       So, if you want to build udev using klibc with debugging messages, you
       would do:
        make USE_KLIBC=true DEBUG=true
 

+      If you want to build the udev helper program cdrom_id and scsi_id you
+      would do:
+       make EXTRAS="extras/cdrom_id extras/scsi_id"
+

       udev will follow the setting of the debug level in udev.conf. Adapt this
       value to see the debug in syslog.
 
       udev will follow the setting of the debug level in udev.conf. Adapt this
       value to see the debug in syslog.
 


@@ -85,7 +92,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
 
 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.
 
 Development and documentation help is very much appreciated, see the TODO
 file for a list of things left to be done.