diff options
| author | Alejandro Colomar <alx@kernel.org> | 2024-11-17 18:47:53 +0100 |
|---|---|---|
| committer | Alejandro Colomar <alx@kernel.org> | 2024-11-17 21:51:23 +0100 |
| commit | 18e7c4597c4e72fa5210c7887273e363c456c9ee (patch) | |
| tree | 97cfd22e731a4c859ae71783d70943ff72e6cb60 /man/man7/user_namespaces.7 | |
| parent | 8fc6fdd8291d906e58a175b5e1b20da680aaeb4a (diff) | |
| download | man-pages-18e7c4597c4e.tar.gz | |
man/: Terminology consistency reforms (n, size, length)
Use 'length' for the lenght of a string.
Use 'n' for the number of elements.
Use 'size' for the number of bytes. (And in wide-character string
functions, 'size' also refers to the number of wide characters.)
The change is quite large, and I might have made some mistakes.
But overall, this should improve consistency in use of these terms.
Signed-off-by: Alejandro Colomar <alx@kernel.org>
Diffstat (limited to 'man/man7/user_namespaces.7')
| -rw-r--r-- | man/man7/user_namespaces.7 | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/man/man7/user_namespaces.7 b/man/man7/user_namespaces.7 index 4131d49270..b8a9331f91 100644 --- a/man/man7/user_namespaces.7 +++ b/man/man7/user_namespaces.7 @@ -413,7 +413,7 @@ The specification in each line takes the form of three numbers delimited by white space. The first two numbers specify the starting user ID in each of the two user namespaces. -The third number specifies the length of the mapped range. +The third number specifies the size of the mapped range. In detail, the fields are interpreted as follows: .IP (1) 5 The start of the range of user IDs in @@ -446,7 +446,7 @@ to see the mapping of user IDs into the user namespace of the process that created this user namespace. .RE .IP (3) -The length of the range of user IDs that is mapped between the two +The size of the range of user IDs that is mapped between the two user namespaces. .P System calls that return user IDs (group IDs)\[em]for example, @@ -483,7 +483,7 @@ $ \fBcat /proc/$$/uid_map\fP This mapping tells us that the range starting at user ID 0 in this namespace maps to a range starting at 0 in the (nonexistent) parent namespace, -and the length of the range is the largest 32-bit unsigned integer. +and the size of the range is the largest 32-bit unsigned integer. This leaves 4294967295 (the 32-bit signed \-1 value) unmapped. This is deliberate: .I (uid_t)\~\-1 @@ -1207,7 +1207,7 @@ usage(char *pname) fpe("\[rs]n"); fpe("Map strings for \-M and \-G consist of records of the form:\[rs]n"); fpe("\[rs]n"); - fpe(" ID\-inside\-ns ID\-outside\-ns len\[rs]n"); + fpe(" ID\-inside\-ns ID\-outside\-ns size\[rs]n"); fpe("\[rs]n"); fpe("A map string can contain multiple records, separated" " by commas;\[rs]n"); @@ -1222,7 +1222,7 @@ usage(char *pname) GID mapping consists of one or more newline\-delimited records of the form: \& - ID_inside\-ns ID\-outside\-ns length + ID_inside\-ns ID\-outside\-ns size \& Requiring the user to supply a string that contains newlines is of course inconvenient for command\-line use. Thus, we permit the |