X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=README;h=a76583ababfed3434e961a9c8a125b5c1e9e9033;hp=00acf97c27e5405b5974a4c373b80f8113e17767;hb=c3f0b654fc18b5f98bc65074e2118177e0f37ae9;hpb=65e9e8c5e8de192b2b6eea0dcb6089268eb9ad2a

diff --git a/README b/README
index 00acf97c2..a76583aba 100644
--- a/README
+++ b/README
@@ -9,7 +9,7 @@ Important Note:
   recommend to replace a distro's udev installation with the upstream version.
 
 Requirements:
-  - Version 2.6.18 of the Linux kernel for reliable operation of this release of
+  - Version 2.6.19 of the Linux kernel for reliable operation of this release of
     udev. The kernel may have a requirement on udev too, see Documentation/Changes
     in the kernel source tree for the actual dependency.
 
@@ -17,19 +17,19 @@ Requirements:
     (unix domain sockets (CONFIG_UNIX) as a loadable kernel module may work,
     but it does not make any sense - don't complain if anything goes wrong.)
 
-  - The proc filesystem must be mounted on /proc, the sysfs filesystem must
-    be mounted at /sys. No other locations are supported by udev.
+  - The proc filesystem must be mounted on /proc/, the sysfs filesystem must
+    be mounted at /sys/. No other locations are supported by udev.
 
 
 Operation:
-  Udev creates and removes device nodes in /dev, based on events the kernel
+  Udev creates and removes device nodes in /dev/, based on events the kernel
   sends out on device discovery or removal.
 
-  - Very early in the boot process, the /dev directory should get a 'tmpfs'
+  - Very early in the boot process, the /dev/ directory should get a 'tmpfs'
     filesystem mounted, which is populated from scratch by udev. Created nodes
     or changed permissions will not survive a reboot, which is intentional.
 
-  - The content of /lib/udev/devices directory which contains the nodes,
+  - The content of /lib/udev/devices/ directory which contains the nodes,
     symlinks and directories, which are always expected to be in /dev, should
     be copied over to the tmpfs mounted /dev, to provide the required nodes
     to initialize udev and continue booting.
@@ -42,50 +42,12 @@ Operation:
     from the kernel driver core.
 
   - All kernel events are matched against a set of specified rules in
-    /etc/udev/rules.d/ which make it possible to hook into the event
+    /lib/udev/rules.d/ which make it possible to hook into the event
     processing to load required kernel modules and setup devices. For all
     devices the kernel exports a major/minor number, udev will create a
     device node with the default kernel name, or the one specified by a
     matching udev rule.
 
-
-Compile Options:
-  DESTDIR
-  	Prefix of install target, used for package building.
-  USE_LOG
-  	If set to 'true', udev is able to pass errors or debug information
-  	to syslog. This is very useful to see what udev is doing or not doing.
-  	It is enabled by default, don't expect any useful answer, if you
-  	need to hunt a bug, but you can't enable syslog.
-  DEBUG
-  	If set to 'true', very verbose debugging messages will be compiled
-  	into the udev binaries. The actual level of debugging is specified
-  	in the udev config file.
-  USE_SELINUX
-  	If set to 'true', udev will be built with SELinux support
-  	enabled.  This is disabled by default.
-  EXTRAS
-  	list of helper programs in extras/ to build.
-        make EXTRAS="extras/cdrom_id extras/scsi_id extras/volume_id"
-
-
-Installation:
-  - The install target intalls the udev binaries in the default locations,
-    All binaries will be installed in /lib/udev or /sbin.
-
-  - The default location for scripts and binaries that are called from
-    rules is /lib/udev. Other packages who install udev rules, may use
-    that directory too.
-
-  - It is recommended to use the /lib/udev/devices/ directory to place
-    device nodes and symlinks in, which are copied to /dev at every boot.
-    That way, nodes for broken subsystems or devices which can't be
-    detected automatically by the kernel, will always be available.
-
-  - Default udev rules and persistent device naming rules are required by other
-    software that depends on the data udev collects from the devices,
-    and should be installed by default with every udev installation.
-
-Please direct any comment/question/concern to the linux-hotplug-devel mailing list at:
+Please direct any comment/question/concern to the linux-hotplug mailing list at:
   linux-hotplug@vger.kernel.org