[PATCH] make /etc/hotplug.d/default/udev.hotplug symlink point to udevsend now.

[elogind.git] / README

diff --git a/README b/README
index fffa7939879a1d814d30425490715dcb907c4497..c63912101a403cfd91dc81adb84591220b56f0a2 100644 (file)
--- a/README
+++ b/README
@@ -8,6 +8,8 @@ To use:
 
 - You must be running a 2.6 version of the Linux kernel.
 
+- Your 2.6 kernel must have had CONFIG_HOTPLUG enabled when it was built.
+
 - Make sure sysfs is mounted.  udev will figure out where sysfs is mounted, but
   the traditional place for it is at /sys.  You can mount it by hand by running:
        mount -t sysfs none /sys
@@ -25,6 +27,41 @@ To use:
 - Build the project:
        make
 
+  Note:
+      There are a number of different flags that you can use when building
+      udev.  They are as follows:
+       prefix
+               set this to the default root that you want udev to be
+               installed into.  This works just like the 'configure --prefix'
+               script does.  Default value is ''.  Only override this if you
+               really know what you are doing.
+       USE_KLIBC
+               if set to 'true', udev is built and linked against the
+               included version of klibc.  Default value is 'false'.
+       USE_LOG
+               if set to 'true', udev will emit messages to the syslog when
+               it creates or removes device nodes.  This is helpful to see
+               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'.
+       DEBUG
+               if set to 'true', debugging messages will be sent to the syslog
+               as udev is run.  Default value is 'false'.
+       KERNEL_DIR
+               If this is not set it will default to /lib/modules/`uname -r`/build
+               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.
+
+      So, if you want to build udev using klibc with debugging messages, you
+      would do:
+       make USE_KLIBC=true DEBUG=true
+
 - Install the project:
        make install
 
@@ -41,21 +78,22 @@ To use:
        make uninstall
 
 
-Things are still quite rough, and it's a bit beyond proof of concept
-code.  Help is very much appreciated, see the TODO file for a list of
-things left to be done.
+Things are still quite rough, but it should work properly.  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.
 
-If you want to build using klibc, use the Makefile.klibc file:
-       - read the klibc/klibc/README file for how to set up the linux
-         symlink properly.
-       - make clean
-       - make -f Makefile.klibc
-and marvel at the tiny binary you just created :)
+Development and documentation help is very much appreciated, see the TODO
+file for a list of things left to be done.
 
-Any comment/questions/concerns please let me know.
+
+Any comment/questions/concerns please let me and the other udev developers
+know by sending a message to the linux-hotplug-devel mailing list at:
+       linux-hotplug-devel@lists.sourceforge.net
 
 greg k-h
 greg@kroah.com
 
 
 
+