summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 1f256f2)
raw | patch | inline | side by side (parent: 1f256f2)
author | Florian Forster <octo@verplant.org> | |
Fri, 2 Sep 2011 02:55:32 +0000 (22:55 -0400) | ||
committer | Florian Forster <octo@verplant.org> | |
Fri, 2 Sep 2011 02:58:29 +0000 (22:58 -0400) |
README | patch | blob | history |
index 5488fb4c66ea3c498c2222d535c5cc8cba817813..95ae19b39dc61f71e56a3949370dd46872203334 100644 (file)
--- a/README
+++ b/README
(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