X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=README;h=92a23724c1a5c7f3bf42013bbcb0a551d065a675;hb=a2ddee73920673aae645ab7fde322251a249024f;hp=2b5fc37d81f6cac70dc8fdc19b5c73d3be338ea5;hpb=5a2cfd1599aa1300e26c2de22b1158c626bc0139;p=elogind.git

diff --git a/README b/README
index 2b5fc37d8..92a23724c 100644
--- a/README
+++ b/README
@@ -3,7 +3,7 @@ udev - Linux userspace device management
 Integrating udev in the system has complex dependencies and may differ from
 distribution to distribution. A system may not be able to boot up or work
 reliably without a properly installed udev version. The upstream udev project
-does not recommend to replace a distro's udev installation with the upstream
+does not recommend replacing a distro's udev installation with the upstream
 version.
 
 The upstream udev project's set of default rules may require a most recent
@@ -62,11 +62,6 @@ Setup:
     works on an empty 'tmpfs' filesystem, but some static device nodes like
     /dev/null, /dev/console, /dev/kmsg are needed to be able to start udev itself.
 
-  - The content of /lib/udev/devices directory which contains static content like
-    symlinks and directories, which are always expected to be in /dev, should
-    be copied over to the mounted /dev directory:
-      cp -axT --remove-destination /lib/udev/devices /dev
-
   - The udev daemon should be started to handle device events sent by the kernel.
     During bootup, the kernel can be asked to send events for all already existing
     devices, to apply the configuration to these devices. This is usually done by: