Bump version to 1.10.0; Update ChangeLog.

[liboping.git] / README

diff --git a/README b/README
index bf8c2bf9341f377ce9476dee78b1012cba7c46c4..8611d7c65f748db7aa37be32b4126e8811cc8c02 100644 (file)
--- a/README
+++ b/README
@@ -1,6 +1,6 @@
  liboping – Library to ping IPv4 and IPv6 hosts in parallel
 ════════════════════════════════════════════════════════════
-http://verplant.org/liboping/
+http://noping.cc/
 
 About
 ━━━━━
@@ -43,6 +43,14 @@ Permissions
   (which is strongly suggested), you won't be able to use the binaries as a
   normal user, because you won't have the permission to open raw sockets.
 
+  The “install” target will automatically try fix this, if it is run with UID~0
+  (as user root).  When on Linux, the capabilities described below will be
+  added. On other UNIXes the traditional Set-UID method (also described below)
+  is used instead. The build system will not abort if this fails, because there
+  are file systems which do not support either method. Also, the Debian
+  packaging system and possibly other scenarios only act as if they were
+  running as root.
+
   Linux
   ━━━━━
   On Linux, the preferred method is to assign the required “capability” to the
@@ -63,7 +71,7 @@ Permissions
   traditional set-UID root solution. If your system supports “saved set-UIDs”
   (basically all systems do), the applications will drop the privileges during
   initialization and only regain them when actually opening the socket(s).
-  
+
   To set the set-UID bit, run (as user root):
 
     # chown root: /opt/oping/bin/{,n}oping