aboutsummaryrefslogtreecommitdiffstats
path: root/man7
AgeCommit message (Collapse)AuthorFilesLines
2024-05-02man/, share/mk/: Move man*/ to man/Alejandro Colomar170-55758/+1
This is a scripted change: $ mkdir man/; $ mv man* man/; $ ln -st . man/man*; $ find share/mk/ -type f \ | xargs grep -l '^MANDIR *:=' \ | xargs sed -i '/^MANDIR *:=/s,$,/man,'; $ find share/mk/dist/ -type f \ | xargs grep -l man \ | xargs sed -i 's,man%,man/%,g'; Link: <https://lore.kernel.org/linux-man/YxcV4h+Xn7cd6+q2@pevik/T/> Cc: Petr Vorel <pvorel@suse.cz> Cc: Jakub Wilk <jwilk@jwilk.net> Cc: Stefan Puiu <stefan.puiu@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-26man*/: EXAMPLES: Add include guardsAlejandro Colomar1-0/+4
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-17ip.7: Some socket options are not supported by SOCK_STREAMOliver Crumrine1-0/+13
It was not made clear in several socket options that they were not supported by SOCK_STREAM; this patch fixes that. Socket options not supported by SOCK_STREAM are handled in the ip_cmsg_recv_offset() function in <net/ipv4/ip_sockglue.c>. The function is called for udp sockets, and indirectly by ping and raw sockets, but not for STREAM sockets, as they don't support these options. Link: <https://lore.kernel.org/linux-man/ejhphmjh74ebtk4br3id66f27a4yoh4aukrcz7m6dp7acsu6zr@crtueyadqzmp/T/#mb298ac7f71a348d1e6b423cfa32bfad9c28efa40> Link: <https://lore.kernel.org/linux-man/ejhphmjh74ebtk4br3id66f27a4yoh4aukrcz7m6dp7acsu6zr@crtueyadqzmp/T/#u> Signed-off-by: Oliver Crumrine <ozlinuxc@gmail.com> Cc: Peter Seiderer <ps.report@gmx.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-16bpf-helpers.7: Refresh pageAlejandro Colomar1-63/+106
Scripted change: $ ~/src/linux/linux/6.8/scripts/bpf_doc.py | rst2man > man7/bpf-helpers.7 Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-16unix.7: EXAMPLES: server.c: End connection with ENDLili Püspök1-1/+5
Client wants to send END while server already closed the connection on DOWN, so connection is broken instead of the Result = 0 in the sample on sending a single DOWN. Now, the server disconnects only on first END. After DOWN, all further processing of number stops. Patch does not handle cases of double END sending, multiple clients etc. Fixes: 15545eb6d7ae ("unix.7: Add example") Cc: Heinrich Schuchardt <xypron.glpk@gmx.de> Signed-off-by: Lili Püspök <poordirtylili@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-14utf-8.7: ffixAlejandro Colomar1-15/+8
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-14utf-8.7: ffixSamanta Navarro1-1/+1
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-12unix.7: Use a 'ssize_t' for the return value of read(2) and write(2)Alejandro Colomar1-21/+23
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-12unix.7: Use 'int' to iterate over 'argv'Alejandro Colomar1-1/+1
'argc' is an 'int', so we should compare it with a variable of the same type. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-12unix.7: Use int main(void)Alejandro Colomar1-1/+1
The arguments were unused. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-12unix.7: Remove spurious #includeAlejandro Colomar1-1/+2
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-12unix.7: Build example programsAlejandro Colomar1-2/+12
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-05cgroups.7: tfixAlejandro Colomar1-2/+2
Closes: <https://bugzilla.kernel.org/show_bug.cgi?id=218105> Reported-by: Göran Uddeborg <goeran@uddeborg.se> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-02-25man*/: srcfixAlejandro Colomar5-34/+34
Found with: $ grep -rn '"""' man* \ | grep -v '"""""""""""' \ | sed 's/:.*//' \ | sort \ | uniq; man2/add_key.2 man2/getrlimit.2 man2/keyctl.2 man2/pivot_root.2 man2/request_key.2 man3/isalpha.3 man3/setlocale.3 man3/toupper.3 man7/capabilities.7 man7/cgroups.7 man7/keyrings.7 man7/locale.7 man7/user_namespaces.7 Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-02-25man*/: ffixAlejandro Colomar1-1/+1
Found with: $ grep -rn '^\.[BI] .* [.,:;)]*$' man* man2/prctl.2:382:.B FR=1 . man2/openat2.2:377:.B EAGAIN . man2/openat2.2:424:.I how.resolve . man5/elf.5:788:.B PF_R . man5/networks.5:18:.I name number aliases ... man5/protocols.5:31:.I protocol number aliases ... man7/cgroups.7:980:.I """max""" . Cc: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-02-25vsock.7: ffixнаб1-1/+1
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-02-18man*/: tfixŠtěpán Němec3-4/+4
Signed-off-by: Štěpán Němec <stepnem@smrk.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-02-18path_resolution.7: Work around groff(1) bugAlejandro Colomar1-1/+1
Link: <https://savannah.gnu.org/bugs/?65320> Link: <https://savannah.gnu.org/bugs/?65322> Link: <https://lists.gnu.org/archive/html/groff/2024-02/msg00039.html> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-01-28charsets.7: Say ISO/IEC 2375Alejandro Colomar1-1/+1
Link: <https://www.iso.org/standard/32184.html> Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-01-28man*/: Say ISO/IEC 646Alejandro Colomar19-20/+20
Link: <https://www.iso.org/standard/4777.html> Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-01-28man*/: Say ISO/IEC 8208Alejandro Colomar2-3/+5
Link: <https://www.iso.org/standard/33080.html> Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-01-28man*/: Say ISO/IEC 8859Alejandro Colomar19-380/+383
Link: <https://www.iso.org/standard/28245.html> Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-01-28man*/: Say ISO/IEC 2022Alejandro Colomar2-10/+10
Link: <https://www.iso.org/standard/22747.html> Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-01-28charsets.7: Say ISO/IEC 4873Alejandro Colomar1-3/+3
Link: <https://www.iso.org/standard/10859.html> Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-01-16socket.7: Mention CAP_NET_RAW on SO_MARKPetr Vorel1-1/+3
Added in 079925cce1d0 ("net: allow SO_MARK with CAP_NET_RAW") in Linux 5.17. Cc: Maciej Żenczykowski <maze@google.com> Cc: Matthias Gerstner <matthias.gerstner@suse.com> Signed-off-by: Petr Vorel <pvorel@suse.cz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-21unix.7: SO_PEERCRED: Mention listen(2)Alexey Tikhonov1-1/+2
In case of connected AF_UNIX stream sockets, server-side credentials are set at the time of a call to listen(2), not when client-side calls connect(2). This is important if server side process changes UID/GID after listen(2) and before connect(2). Reproducer is available in [1]. Behavior was confirmed in the email thread [2]. Link: [1] <https://bugzilla.redhat.com/show_bug.cgi?id=2247682> Link: [2] <https://lore.kernel.org/linux-man/CABPeg3a9L0142gmdZZ+0hoD+Q3Vgv0BQ21g8Z+gf2kznWouErA@mail.gmail.com/> Signed-off-by: Alexey Tikhonov <atikhono@redhat.com> Reviewed-by: Kuniyuki Iwashima <kuniyu@amazon.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-17string_copying.7: EXAMPLES: st[rp]ncpy(3): Use fwrite(3) instead of a loopAlejandro Colomar1-4/+2
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-17string_copying.7: Use NITEMS() instead of sizeof()Alejandro Colomar1-14/+14
For these byte functions, sizeof() works as well as NITEMS(), since CHAR_BIT == 1. However, equivalent wide-character functions need NITEMS(), which is semantically more appropriate, and also safer (it cannot be applied to pointers). Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-17string_copying.7: EXAMPLES: Update stpecpy() exampleAlejandro Colomar1-2/+2
The function was changed recently to return NULL on truncation; update the example of use accordingly. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-17string_copying.7: stpecpy(): Reimplement as a wrapper of strtcpy()Alejandro Colomar1-16/+3
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-17string_copying.7: stpecpy(): Return NULL on truncationAlejandro Colomar1-19/+19
This makes it simpler to test the return value, and since it sets errno to find out the reason, we don't need a complex return value. Now that (dst == end) shouldn't happen, use ENOBUFS to report that error. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-17string_copying.7: stpecpy(), strtcpy(): Set errno on failureAlejandro Colomar1-4/+36
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-05string_copying.7: wfixAlejandro Colomar1-1/+3
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-05string_copying.7: Generalize null-padded character sequences with strnlen(3)Alejandro Colomar1-12/+7
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-04string_copying.7: Be consistent in the use of null byte and null characterAlejandro Colomar1-12/+13
Null character, for the terminating character of a string. Null byte, for the padding. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-04string_copying.7: Don't say 'size' when 'len' is meantAlejandro Colomar1-6/+6
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-04string_copying.7: Say 'known-length' for character sequences whose length is ↵Alejandro Colomar1-10/+10
known Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-04string_copying.7: Don't say 'width' when 'size' is meantAlejandro Colomar1-9/+9
Reported-by: Paul Eggert <eggert@cs.ucla.edu> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-04string_copying.7: RETURN VALUE: Remove some confusing text about stpncpy(3)Alejandro Colomar1-7/+2
That text could lead someone to think that it's possible to check truncation from the return value, but it isn't. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-04string_copying.7: Consistently list strtcpy() after stpecpy()Alejandro Colomar1-43/+43
And put it next to strlcpy(3bsd), which is very similar to strtcpy(). Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-04string_copying.7: stpecpy() and strtcpy() don't exist in man3Alejandro Colomar1-19/+19
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-04string_copying.7: Use fwrite(3) to print character sequencesAlejandro Colomar1-2/+2
Suggested-by: Paul Eggert <eggert@cs.ucla.edu> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-04string_copying.7: tfixAlejandro Colomar1-1/+1
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-04string_copying.7: Use real examples with utmp(5)Alejandro Colomar1-22/+16
For the functions that are designed to be used with utmp(5) or similar APIs, use utmp(5) in the example, which results in a clearer example, and also more realistic. It better clarifies how these functions are to be used. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-04string_copying.7: Improve strncat(3) exampleAlejandro Colomar1-4/+5
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-04string_copying.7: Reimplement stpecpy()Alejandro Colomar1-8/+9
This implementation resembles more strtcpy(), so the differences are more visible. Also, it has no -1's, so it's a bit easier to implement correctly. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-04string_copying.7: Remove zustr2stp()Alejandro Colomar1-46/+13
Instead, document how to use mempcpy(3) well in that case. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-04string_copying.7: Remove zustr2ustp()Alejandro Colomar1-39/+10
Instead, document how to use mempcpy(3) well in that case. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-03string_copying.7: Remove ustr2stp() and ustpcpy()Alejandro Colomar1-67/+23
Users reported complains about having so many invented functions, and the complexity of remembering all of them. In these two cases, open-coding mempcpy(3) isn't so bad. In fact, it's quite readable. It has the problem of type safety, since this function accepts almost everything, but let users come up with a wrapper if they need it; it's not like you would be calling these functions often. Document how to use mempcpy(3) well in those cases. Cc: "Serge E. Hallyn" <serge@hallyn.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-12-03string_copying.7: Fortify source of some functionsAlejandro Colomar1-17/+4
By setting the terminating null byte via a stpcpy(dst, "") call, the last byte is also protected by _FORTIFY_SOURCE. Reported-by: "Serge E. Hallyn" <serge@hallyn.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-19man*/: srcfixG. Branden Robinson2-6/+14
Clean up in preparation for "MR sed". Format only one man page cross reference per input line. Begin parentheticals on their own input lines. Also, groff 1.23.0's (and Plan 9 from User Space's) `MR` is not a font style alternation macro; there is no "reversed" form as with `BR` and `RB`. So when a man page cross reference must be immediately preceded by punctuation, put that punctuation on the previous text line and use the `\c` escape sequence to connect them. Signed-off-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-13string_copying.7: Recommend failing instead of truncatingAlejandro Colomar1-1/+4
Especially for validating input, code should fail, not truncate. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-13string_copying.7: Use 'dsize' and 'ssize' for 'dst size' and 'src size'Alejandro Colomar1-25/+25
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-12string_copying.7: Add strtcpy(3)Alejandro Colomar1-29/+68
Add this new truncating string-copying function. It intends to fully replace strlcpy(3), which has important bugs (documented in the preceeding commit). It is almost identical to Linux kernel's strscpy(9), so reduce the documentation of strscpy(9) in this page to the minimum, giving preference to strtcpy(3). Provide a reference implementation, since no libc provides it. Providing an easy, safe, and relatively fast truncating string-copying function should prevent users from rolling their own, in which they might introduce bugs accidentally. We already made enough mistakes while discussing these functions, so it's certainly not something that should be written often. Cc: Paul Eggert <eggert@cs.ucla.edu> Cc: Jonny Grant <jg@jguk.org> Cc: DJ Delorie <dj@redhat.com> Cc: Matthew House <mattlloydhouse@gmail.com> Cc: Oskari Pirhonen <xxc3ncoredxx@gmail.com> Cc: Thorsten Kukuk <kukuk@suse.com> Cc: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org> Cc: Zack Weinberg <zack@owlfolio.org> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Cc: Carlos O'Donell <carlos@redhat.com> Cc: Xi Ruoyao <xry111@xry111.site> Cc: Stefan Puiu <stefan.puiu@gmail.com> Cc: Andreas Schwab <schwab@linux-m68k.org> Cc: Guillem Jover <guillem@hadrons.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-12string_copying.7: BUGS: Document strl{cpy,cat}(3)'s performance problemsAlejandro Colomar1-1/+17
Also point to BUGS from other sections that talk about these functions. These functions are doomed due to the design decision of mirroring snprintf(3)'s return value. They must return strlen(src), which makes them terribly slow, and vulnerable to DoS if an attacker can control strlen(src). A better design would have been to return -1 when truncating. Reported-by: Paul Eggert <eggert@cs.ucla.edu> Cc: Jonny Grant <jg@jguk.org> Cc: DJ Delorie <dj@redhat.com> Cc: Matthew House <mattlloydhouse@gmail.com> Cc: Oskari Pirhonen <xxc3ncoredxx@gmail.com> Cc: Thorsten Kukuk <kukuk@suse.com> Cc: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org> Cc: Zack Weinberg <zack@owlfolio.org> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Cc: Carlos O'Donell <carlos@redhat.com> Cc: Xi Ruoyao <xry111@xry111.site> Cc: Stefan Puiu <stefan.puiu@gmail.com> Cc: Andreas Schwab <schwab@linux-m68k.org> Cc: Guillem Jover <guillem@hadrons.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-12string_copying.7: BUGS: *cat(3) functions aren't always badAlejandro Colomar1-0/+6
The compiler will sometimes optimize them to normal *cpy(3) functions, since the length of dst is usually known, if the previous *cpy(3) is visible to the compiler. And they provide for cleaner code. If you know that they'll get optimized, you could use them. Cc: Paul Eggert <eggert@cs.ucla.edu> Cc: Jonny Grant <jg@jguk.org> Cc: DJ Delorie <dj@redhat.com> Cc: Matthew House <mattlloydhouse@gmail.com> Cc: Oskari Pirhonen <xxc3ncoredxx@gmail.com> Cc: Thorsten Kukuk <kukuk@suse.com> Cc: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org> Cc: Zack Weinberg <zack@owlfolio.org> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Cc: Carlos O'Donell <carlos@redhat.com> Cc: Xi Ruoyao <xry111@xry111.site> Cc: Stefan Puiu <stefan.puiu@gmail.com> Cc: Andreas Schwab <schwab@linux-m68k.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-12string_copying.7: wfixAlejandro Colomar1-4/+4
Don't start this paragraph with a fragment. Also, remove "by nature", which is superfluous. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-12string_copying.7: DESCRIPTION::Functions: ustpcpy() and ustr2stp() are not ↵Alejandro Colomar1-0/+6
provided by any libc Reported-by: Jonny Grant <jg@jguk.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-12string_copying.7: RETURN VALUE: ffixAlejandro Colomar1-42/+28
Put the text after the function names, like the rest of the page. Suggested-by: Jonny Grant <jg@jguk.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-12string_copying.7: wfixAlejandro Colomar1-15/+15
Remove superfluous words. Suggested-by: Jonny Grant <jg@jguk.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-11hostname.7: ffixAlejandro Colomar1-1/+1
Add missing man-page reference. Fixes: 921e2cfd1fc6 ("hostname.7: HOSTALIASES/search path processing is DNS-specific") Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-09stpncpy.3, string.3, string_copying.7: Clarify that st[rp]ncpy() pad with ↵Alejandro Colomar1-1/+2
null bytes The previous wording could be interpreted as if the nulls were already in place. Clarify that it's this function which pads with null bytes. Also, it copies "characters" from the src string. That's a bit more specific than copying "bytes", and makes it clearer that the terminating null byte in src is not part of the copy. Suggested-by: Jonny Grant <jg@jguk.org> Cc: DJ Delorie <dj@redhat.com> Cc: Matthew House <mattlloydhouse@gmail.com> Cc: Oskari Pirhonen <xxc3ncoredxx@gmail.com> Cc: Thorsten Kukuk <kukuk@suse.com> Cc: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org> Cc: Zack Weinberg <zack@owlfolio.org> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Cc: Carlos O'Donell <carlos@redhat.com> Cc: Paul Eggert <eggert@cs.ucla.edu> Cc: Xi Ruoyao <xry111@xry111.site> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-09stpncpy.3, string_copying.7: Clarify that st[rp]ncpy() do NOT produce a stringAlejandro Colomar1-10/+10
These copy *from* a string. But the destination is a simple character sequence within an array; not a string. Suggested-by: DJ Delorie <dj@redhat.com> Acked-by: Oskari Pirhonen <xxc3ncoredxx@gmail.com> Cc: Jonny Grant <jg@jguk.org> Cc: Matthew House <mattlloydhouse@gmail.com> Cc: Thorsten Kukuk <kukuk@suse.com> Cc: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org> Cc: Zack Weinberg <zack@owlfolio.org> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Cc: Carlos O'Donell <carlos@redhat.com> Cc: Paul Eggert <eggert@cs.ucla.edu> Cc: Xi Ruoyao <xry111@xry111.site> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-01regex.7: ffixAlejandro Colomar1-1/+1
Fixes: de9137cb670e ("man-pages 1.20") Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-01posixoptions.7: pfixAlejandro Colomar1-1/+1
Fixes: 17282a589f2f ("posixoptions.7: Make function lists more consistent and less cluttered") Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-01man*/: wfix (say 'null pointer', not 'NULL pointer')Alejandro Colomar1-1/+1
'NULL' is a null pointer _constant_. A 'null pointer' is a broader concept. 'NULL pointer' is not a thing. See the link below. Link: <https://software.codidact.com/posts/278657> Fixes: 9517cf56fcbd ("pidfd_send_signal.2: New page documenting pidfd_send_signal(2)") Fixes: fcd1bee32aa9 ("bpf.2: Improvements after comments from Daniel Borkmann") Fixes: 5d92031a43b4 ("execve.2: Explicitly note that argv[argc] == NULL in the new program") Fixes: 9f79744c9af3 ("keyctl.2: Improve KEYCTL_INSTANTIATE details") Fixes: 1b6ab34c5320 ("attributes.7: New page describing POSIX safety concepts") Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-10-31man*/: srcfix (Use .P instead of .PP or .LP)Alejandro Colomar98-1911/+1911
We're trying to "standardize" on a paragraphing macro from the three equivalent ones (P, PP, LP). We (somewhat arbitrarily) agreed on P. Scripted change: $ find man* -type f | xargs sed -i '/\.PP/s/PP/P/' $ find man* -type f | xargs sed -i '/\.LP/s/LP/P/' Suggested-by: "G. Branden Robinson" <branden@debian.org> Cc: Ingo Schwarze <schwarze@openbsd.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-10-23man*/: ffix (Use '.TQ' where appropriate)Alejandro Colomar9-38/+153
When there are multiple tags for a paragraph, using a single TP and separating the tags with commas makes the man(7) source more complex. It also has a disadvantage: when searching through a manual page, heuristics such as " --option" don't work so well. By using GNU's TQ, we simplify the source of the pages, and improve the ability to search them. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-10-18man*/: ffix: Follow rules for lists from man-pages(7)Alejandro Colomar3-4/+4
Including in commented out lists, so that grep(1) doesn't show odd cases. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-10-15fanotify.7: Fix field name in struct fanotify_event_info_fidMatthew House1-8/+9
The final field of this struct as defined in include/uapi/linux/fanotify.h (and as used in the example program) is called handle, not file_handle. Fix this, and also replace the zero-length array with a flexible array member to match the definition in the header. Fixes: 0a4db6dc742d ("fanotify.7, fanotify_init.2, fanotify_mark.2: Document FAN_REPORT_FID and directory modification events") Signed-off-by: Matthew House <mattlloydhouse@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-10-12string_copying.7: Clarify 'ustr' and 'zustr'Alejandro Colomar1-0/+7
Suggested-by: "Serge E. Hallyn" <serge@hallyn.com> Acked-by: "Serge E. Hallyn" <serge@hallyn.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-09-27system_data_types.7: Clarify si_addr field.Elliott Hughes1-1/+1
This patch reuses the clearer text from sigaction.2 instead. I've also filed https://www.austingroupbugs.net/view.php?id=1775 to improve POSIX's wording here to not be SIGILL-specific. Signed-off-by: Elliott Hughes <enh@google.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-09-22man*/: Update references to sigevent(7 => 3type)Alejandro Colomar3-3/+3
Acked-by: Elliott Hughes <enh@google.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-09-22sigevent.3type, sigevent.7: Merge sigevent(7) into sigevent(3type)Alejandro Colomar1-120/+1
Keep the old page, sigevent(7), as a link page to the one in 3type. Acked-by: Elliott Hughes <enh@google.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-09-22sigevent.3type, sigval.3type, system_data_types.7: Move sigval to sigevent.3typeAlejandro Colomar1-31/+0
Acked-by: Elliott Hughes <enh@google.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-09-22sigevent.3type, system_data_types.7: Move sigevent to its own pageAlejandro Colomar1-47/+0
Acked-by: Elliott Hughes <enh@google.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-09-13inode.7: tfix: Correct the field name for number of blocksAvinesh Kumar1-1/+1
Fixes: b48c75727c64 ("inode.7: New page with information about inodes") Signed-off-by: Avinesh Kumar <akumar@suse.de> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-09-13inode.7: Remove duplicate field nameAvinesh Kumar1-1/+0
Fixes: b48c75727c64 ("inode.7: New page with information about inodes") Signed-off-by: Avinesh Kumar <akumar@suse.de> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-29man.7: Replace page with `so` of groff_man(7)G. Branden Robinson1-507/+1
Suggested-by: Alejandro Colomar <alx@kernel.org> Acked-by: Ingo Schwarze <schwarze@usta.de> Signed-off-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-29strcpy.3, strncat.3, string_copying.7: tfixAlejandro Colomar1-1/+1
Remove non-breaking space (0xC2A0) that accidentally landed in the source of some string pages. Replace by a normal space (0x20). Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-13man*/: Replace .sp 1 calls by PP or IPAlejandro Colomar3-12/+12
They were used after a table as a workaround for a groff-1.22.4 bug, but now, in groff-1.23.0, we can use the usual PP or IP macros. Link: <https://savannah.gnu.org/bugs/index.php?49390> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-13man*/: Remove .sp 1 calls right before SH or PPAlejandro Colomar1-1/+0
Scripted patch: $ grep -rl '^\.sp ' man* | xargs sed -z -i 's/\n\.TE\n\.sp 1\n\.SH/\n.TE\n.SH/' $ grep -rl '^\.sp ' man* | xargs sed -z -i 's/\n\.TE\n\.sp 1\n\.PP/\n.TE\n.PP/' plus a few other cases where roff(7) comments made it more complex. This was a workaround for some groff-1.22.4 bug, but it has been fixed in groff-1.23.0. Link: <https://savannah.gnu.org/bugs/index.php?49390> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-07-30ipv6.7: srcfixG. Branden Robinson1-3/+2
Protect literals in a (very long) paragraph tag from hyphenation by using hypenation control escape sequences, instead of `nh` and `hy` requests. The latter approach is incorrect for use with groff(1) since '.hy' does not restore the previous hyphenation mode but sets it to 1, which is not appropriate for the English-language hyphenation patterns groff uses. (Also, AT&T man(7) used a hyphenation mode of 14.) Also wrap long input line with \newline escape sequence. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-07-30man*/: ffix (un-bracket tables, continued)G. Branden Robinson2-16/+0
Continue commit 9e54434ead, 19 July. 4 pages issued requests to manipulate adjustment and automatic hyphenation around tbl(1) tables in a different order from the other 525 documents in the tree that performed this trick. I produced this change with the following GNU sed script. /^\.nh/{N;/\n\.ad l/{N;/\n\.TS/s/.*/.TS/}} /^\.TE/{N;/\n\.ad/{N;/\n\.hy/s/.*/.TE/}} Fizes: 9e54434ead ("man*/: ffix (un-bracket tables)") Signed-off-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-07-29string_copying.7: tfixLennart Jablonka1-11/+11
On some of the commas: There are a few of instances of Subject verb object partclause, advphrase. For example: This function catenates the input character sequence | subject | verb | object | contained in a null-padded wixed-width buffer, | participial clause | into a destination string. | adverbial phrase | Imagining the participial clause away, there shouldn't be a comma preceding the restrictive adverbial phrase: The input character sequence is really, always catenated into a destination string; that is essential. For example: This function catenates the input character sequence into a destination string. The participial clause, being non-restrictive---there is but one input character sequence that could be meant---, should be enclosed by commas. That is the existing comma's purpose and doesn't work without the added, first comma. Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Lennart Jablonka <humm@ljabl.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-07-29man.7: ffixG. Branden Robinson1-1/+1
The `\c` escape sequence works in an argument to a macro call that is part of a paragraph tag with font style alternation macros, but not the ordinary font macros `B` and `I`. This is because `TP`, `B`, and `I` all set up input traps; the six font style alternation macros do not. The old formatting would, for some versions of some formatters, set the "[trailer]" text as part of the paragraph body, not the tag--like this. .UE [trailer] Terminate the link text of the preceding .UR macro, with the optional trailer (if present, usually a (and so on) This was a poorly understood--and undocumented--interaction of man(7) features until recently. Gory details involving nroff on Unix Version 7 (1979) running on a simulated PDP-11/45 are available.[1] Here is a comparison of the former and new markup. before ====== groff 1.22.3: BAD groff 1.22.4: GOOD groff 1.23.0: BAD mandoc 1.14.6: BAD now === groff 1.22.3: BAD groff 1.22.4: GOOD groff 1.23.0: GOOD mandoc 1.14.6: GOOD [1] https://savannah.gnu.org/bugs/?51468 https://lists.gnu.org/archive/html/groff/2022-06/msg00020.html Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-07-29string_copying.7: don't grant strl{cpy,cat} magicLennart Jablonka1-5/+1
A function can't check whether a pointer points to the start of a string. What it certainly can do is to keep reading until you either find a null byte or read the secret key that lies adjacent in memory and post it to your favorite mailing list. strlcpy and strlcat behave the exact same way any other function accepting a string behaves: If you don't pass a string, the behavior is undefined. And that, I believe, does not deserve a special mention here, seeing as all the other string functions don't get such a mention either. Link: <https://lore.kernel.org/linux-man/ZMQVYtquNN-s0IJr@beryllium/T/#u> Signed-off-by: Lennart Jablonka <humm@ljabl.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-07-28man*/: srcfixG. Branden Robinson1-2/+2
[Clean up in preparation for "MR sed".] Drop spurious, nilpotent uses of *roff `\c` escape sequence. Quoting groff_man_style(7): \c End a text line without inserting space or attempting a break. Normally, if filling is enabled, the end of a text line is treated like a space; an output line _may_ be broken there (if not, an adjustable space is inserted); if filling is disabled, the line _will_ be broken there, as in .EX/.EE examples. The next line is interpreted as usual and can include a macro call (contrast with \newline). \c is useful when three font styles are needed in a single word, as in a command synopsis. Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-07-28man.7: srcfixG. Branden Robinson1-35/+35
[Clean up in preparation for "MR sed".] Drop spurious uses of *roff `\&` escape sequence. Quoting groff_man_style(7): \& Dummy character. Insert at the beginning of an input line to prevent a dot or apostrophe from being interpreted as beginning a roff control line. Append to an end‐of‐sentence punctuation sequence to keep it from being recognized as such. Neither case applies to the uses in this page. Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-07-20man*/: ffix (un-bracket tables)G. Branden Robinson1-4/+0
* Stop disabling adjustment and automatic hyphenation before tables, and incorrectly "restoring" it afterward. In addition to repetitious boilerplate around tables, the `ad` and `hy` requests, when not given arguments, do not behave as many man page authors expect. If adjustment was initially disabled when rendering the page, it was being activated after `TE` calls, frustrating the desire of the reader. Furthermore, `hy` when given no argument enables automatic hyphenation in mode "1", which is not an appropriate value for the TeX-based hyphenation patterns for English that groff has used for over 30 years. And analogously to `ad`, a simple `hy` request would reactivate automatic hyphenation even if the reader had disabled it. Moreover, such fiddling is often unnecessary. tbl(1) from groff 1.23.0 describes how tbl(1) has always worked, dating back to Michael Lesk's original implementation at Bell Labs in the 1970s. "Ordinarily, a table entry is typeset rigidly. It is not filled, broken, hyphenated, adjusted, or populated with additional inter- sentence space. ... Text blocks are formatted as was the text prior to the table, modified by applicable column descriptors. ... Add na or ad requests to the beginning of a text block to alter its adjustment distinctly from other text in the document. As with other table entries, when a text block ends, any alterations to formatting parameters are discarded. They do not affect subsequent table entries, not even other text blocks." * Apropos of the foregoing, add `na` and `nh` requests to the "Interface" columns of MT-safety tables in pages' "ATTRIBUTES" sections, so that C function names are not inappropriately hyphenated. I produced this change with the following GNU sed script. :start /^\.ad l/{N;/\n\.nh/{N;/\n\.TS/s/.*/.TS/}} /^\.TE/{N;/\n\.hy/{N;/\n\.ad/s/.*/.TE/}} /^Interface.*Attribute.*Value/{N;/\nT{/s/.*/&\n.na\n.nh/ :loop n /T{/s/.*/&\n.na\n.nh/ /^\.TE/b start; b loop } Signed-off-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-07-18complex.7: Add LIBRARY section (libm)Alejandro Colomar1-1/+3
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-07-18cpuset.7: wfixAlejandro Colomar1-2/+6
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-07-16pipe.7: document read()s with O_NONBLOCKнаб1-1/+8
Which don't behave like you may expect them to; unprimed, I expected the natural extension of either: files (being a filesystem object), always returning 0 if no data, or sockets (being an IPC mechanism), always EAGAINing if no data. The pipe semantics make sense of course ‒ pipes can be modelled as sockets if there aren't writers, but files if there are; indeed, this makes sense as the writer continuously appending a sliding "window" over a file ‒ but they're unique amongst the UNIX file types, but arriving at that specific interaction table is non-obvious, especially to a user. Quoth Issue 8 Draft 3: 60746 When attempting to read from an empty pipe or FIFO: 60747 • If no process has the pipe open for writing, read( ) shall return 0 to indicate end-of-file. 60748 • If some process has the pipe open for writing and O_NONBLOCK is set, read( ) shall return 60749 −1 and set errno to [EAGAIN]. 60750 • If some process has the pipe open for writing and O_NONBLOCK is clear, read( ) shall 60751 block the calling thread until some data is written or the pipe is closed by all processes that 60752 had the pipe open for writing. Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-07-15man*/: Use SPDX-License-Identifier: Linux-man-pages-1-paraAlejandro Colomar14-97/+28
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-07-15socket.7: tfixEric Biggers1-1/+1
Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-07-15man*/: Prefer off_t over off64_t for splice(2), etc.Paul Eggert1-4/+8
For the few functions that come only in 64-bit off_t flavors, document their APIs as using off_t instead of off64_t, and say also that code should #define _FILE_OFFSET_BITS 64. This documents what user code is (and should be) doing anyway, if it needs to work on traditional x86 and ARM Linux. Reported-by: Rich Felker <dalias@libc.org> Fixes: 9bebb17e5b57 ("splice.2: Use 'off64_t' instead of 'loff_t'") Fixes: 76c5631fb442 ("copy_file_range.2: Document glibc wrapper instead of kernel syscall") Fixes: 5cabfa06b407 ("man-pages 1.68") Fixes: 3ca974e3988a ("New page for sync_file_range(2), new in kernel 2.6.17.") Fixes: 9bebb17e5b57 ("sync_file_range.2: Document the architecture-specific sync_file_range2() system call") Fixes: 79bf8cdcf36a ("Document fopencookie(3), a library function that allows custom implementation of a stdio stream.") Signed-off-by: Paul Eggert <eggert@cs.ucla.edu> Reviewed-by: Sam James <sam@gentoo.org> Cc: Jonathan Wakely <jwakely@redhat.com> Cc: Szabolcs Nagy <nsz@port70.net> Cc: Jakub Wilk <jwilk@jwilk.net> Cc: A. Wilcox <AWilcox@wilcox-tech.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-07-08ip.7: Document IP_LOCAL_PORT_RANGE socket optionJakub Sitnicki1-0/+26
Linux commit 91d0b78c5177 ("inet: Add IP_LOCAL_PORT_RANGE socket option") introduced a new socket option available for AF_INET and AF_INET6 sockets. Option is available starting from Linux 6.3. Document it. Reviewed-by: Simon Horman <simon.horman@corigine.com> Signed-off-by: Jakub Sitnicki <jakub@cloudflare.com> [alx: semantic newlines] Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-07-08inotify.7: wds are in the range [1, INT_MAX], not [0,наб1-1/+1
Naturally, the first inotify_add_watch() returns 1, but also fs/notify/inotify.c:inotify_add_to_idr() allocates them with idr_alloc_cyclic(idr, i_mark, start=1, end=0, GFP_NOWAIT); (start inclusive, end exclusive). (From SYSCALL_DEFINE3(inotify_add_watch, ...), from inotify_update_watch(), from inotify_new_watch()). Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-07-08boot.7: LILO is not used often anymoreAlejandro Colomar1-4/+4
On 6/18/23 22:05, Oskari Pirhonen wrote: > On Sat, Jun 17, 2023 at 13:11:29 +0200, Helge Kreutzmann wrote: >> Hello Alejandro, >> On Sun, Mar 12, 2023 at 12:31:37AM +0100, Alejandro Colomar wrote: >>> On 3/11/23 18:13, Helge Kreutzmann wrote: >>>> Without further ado, the following was found: >>>> >>>> Issue: This is true only on x86 and Lilo is probably not much >>>> used anymore; also systemd has its own (?) bootloader >> >> Lilo has just been removed from Debian, so to my knowledge only >> Mageia ships it. >> > > FWIW, Gentoo still has LILO in the repos. This doesn't change the > fact that it probably does not see much use anymore. Definitely not > enough to warrant being mentioned as "is often". Maybe a historical > note, if anything. Reported-by: Helge Kreutzmann <debian@helgefjell.de> Reported-by: Oskari Pirhonen <xxc3ncoredxx@gmail.com> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-05-26ddp.7: Relicense to Linux-man-pages-copyleftAlejandro Colomar1-6/+1
Alan Cox gave me explicit permission to relicense it for consistency with the rest of the project. Cc: Alan Cox <alan@llwyncelyn.cymru> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-05-20system_data_types.7: tfixEric Wong1-2/+2
The actual field names omit the 'g', matching sigevent.7. Signed-off-by: Eric Wong <e@80x24.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-05-03man*/, man.ignore.grep: srcfix; warn about blank linesAlejandro Colomar25-433/+432
- Use the dummy character to avoid warnings in examples. - Re-enable the warning. Suggested-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-05-02ascii.7: ffixAlejandro Colomar1-17/+5
Simplify formatting of ASCII tables. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-30uri.7: ffixAlejandro Colomar1-20/+79
Reported-by: groff(1) (`make build-catman-troff`) Cowritten-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-29man*/: srcfixAlejandro Colomar1-1/+1
Reported-by: groff(1) (`make build-catman-troff`) Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-29man*/: ffixAlejandro Colomar2-9/+9
Reported-by: groff(1) (`make built-catman-troff`) Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-23man*/: wfixGünther Noack1-1/+1
Fix spelling of "run time", as documented in man-pages(7): - "run time" in two words when used as a noun - "run-time" with hyphen when used as an adjective There is another occurrence in bpf-helpers.7, but that content gets generated from the kernel source and should be fixed there. Signed-off-by: Günther Noack <gnoack3000@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-19landlock.7: Return instead of exit() if Landlock is unusableGünther Noack1-1/+1
When following a best effort approach, we should not fail when Landlock is unusable, but we should fall back to doing nothing. Link: <https://lore.kernel.org/linux-man/5d90e3b0-1577-7efd-03b8-f94b6e50fbc1@digikod.net/> Suggested-by: Mickaël Salaün <mic@digikod.net> Signed-off-by: Günther Noack <gnoack3000@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-19landlock.7: wfix: Error message wording in code exampleGünther Noack1-1/+1
Link: <https://lore.kernel.org/linux-man/5d90e3b0-1577-7efd-03b8-f94b6e50fbc1@digikod.net/> Suggested-by: Mickaël Salaün <mic@digikod.net> Signed-off-by: Günther Noack <gnoack3000@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-19landlock.7: Use LANDLOCK_* constants for compatibility tableGünther Noack1-3/+3
Link: <https://lore.kernel.org/linux-man/5d90e3b0-1577-7efd-03b8-f94b6e50fbc1@digikod.net/> Cc: Mickaël Salaün <mic@digikod.net> Signed-off-by: Günther Noack <gnoack3000@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-19landlock.7: Check syscall result with == -1 instead of <= 0Günther Noack1-1/+1
Link: <https://lore.kernel.org/linux-man/5d90e3b0-1577-7efd-03b8-f94b6e50fbc1@digikod.net/> Reported-by: Mickaël Salaün <mic@digikod.net> Signed-off-by: Günther Noack <gnoack3000@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-18man*/: ffixGuillem Jover3-3/+3
Escape dashes on UUIDs, URLs, and file and package names. Signed-off-by: Guillem Jover <guillem@hadrons.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-17landlock.7: Explain the best-effort fallback mechanism in the exampleGünther Noack1-4/+69
Signed-off-by: Günther Noack <gnoack3000@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-14ip.7: ffixAlejandro Colomar1-6/+6
Fixes: 51f5698d3ce9 "...: ffix: replace .sp by .PP" Fixes: 6545cc56e02e "...: ffix" Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-14ip.7: Add "Special and reserved addresses" sectionSeth David Schoen1-8/+72
Break out the discussion of special and reserved IPv4 addresses into a subsection, formatted as a pair of definition lists, and briefly describing three cases in which Linux no longer treats addresses specially, where other systems do or did. Also add a specific example to the NOTES paragraph that discourages the use of IP broadcasting, so people can more easily understand what they are supposed to do instead. Suggested-by: John Gilmore <gnu@toad.com> Signed-off-by: Seth David Schoen <schoen@loyalty.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-11bpf-helpers.7: Refresh page (Linux 6.2)Alejandro Colomar1-197/+243
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-08rtnetlink.7: Document IFLA_PERM_ADDRESSLinus Heckemann1-0/+3
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-05feature_test_macros.7: Document Clang fortify supportMingye Wang1-7/+7
This commit lists both gcc and clang versions. It also happens to fix the "glibc 4.0" mistake in b324e17d3208c940622ab192609b836928d5aa8d. Fixes: b324e17d3208 ("Many pages: wfix") Signed-off-by: Mingye Wang <arthur200126@gmail.com> Acked-by: Sam James <sam@gentoo.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-05man*/: srcfixAlejandro Colomar2-2/+2
Reported-by: mandoc(1) (`make lint-man-mandoc`) Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-03man*/: ffixAlejandro Colomar8-15/+17
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-02landlock.7: Fix warningsAlejandro Colomar1-1/+2
Reported-by: `make lint check` Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-01user_namespaces.7: Add note about PR_SET_DUMPABLE on nested usernsRodrigo Campos1-0/+17
In order to create a nested user namespace, we need to re-set the PR_SET_DUMPABLE attribute after switching the effective UID/GID. Clarify this in the section about nested user namespaces. Having this note would have saved me some time debugging. Signed-off-by: Rodrigo Campos <rodrigo@sdfg.com.ar> Cc: Christian Brauner <brauner@kernel.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-01landlock.7: Document Landlock ABI v3 (file truncation; Linux 6.2)Günther Noack1-2/+81
https://git.kernel.org/torvalds/c/299e2b1967578b1442128ba8b3e86ed3427d3651 Signed-off-by: Günther Noack <gnoack3000@gmail.com> Reviewed-by: Mickaël Salaün <mic@digikod.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-01landlock.7: Document Landlock ABI v2 (file reparenting; Linux 5.19)Günther Noack1-2/+100
* Add the description for LANDLOCK_ACCESS_FS_REFER, in line with recent update to the uapi headers: https://lore.kernel.org/linux-security-module/20230202204623.10345-1-gnoack3000@gmail.com/T/ * VERSIONS: Add a table of Landlock versions and their changes. Briefly talk about how to probe ABI levels and warn users about the special semantics of the LANDLOCK_ACCESS_FS_REFER right. * Add LANDLOCK_ACCESS_FS_REFER to the code example. Code review threads for the "refer" feature: * https://git.kernel.org/torvalds/c/cb44e4f061e16be65b8a16505e121490c66d30d0 * https://lore.kernel.org/all/20230221165205.4231-1-gnoack3000@gmail.com/ (documentation update) Signed-off-by: Günther Noack <gnoack3000@gmail.com> Reviewed-by: Mickaël Salaün <mic@digikod.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-31symlink.7: cross-link to proc.5 for fs.protected_symlinksнаб1-2/+6
This is on by default in Debian, maybe the next reader won't spend an hour tracing the kernel Fixes: e8ff4f53ab9a7cbd ("Remove information migrated to inode(7) page") Closes: https://bugs.debian.org/1033477 Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Cc: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-30man*/, man-pages.7: VERSIONS, STANDARDS, HISTORY: Reorganize sectionsAlejandro Colomar16-65/+74
- Add a new HISTORY section that covers the history of an API, both regarding implementations and regarding old standards. This was previously covered in VERSIONS, and in some cases in STANDARDS. - Repurpose VERSIONS to cover differing implementations in _current_ systems. - STANDARDS is reduced to only cover current versions of standards. That basically means only C11 (C99 has been superseeded by C11; C17 is just a bugfix of C11, so not really a new version), and POSIX.1-2008 (*-2001 was superseeded by *-2008; *-2017 was just a bugfix for *-2008). The section also mentions for example 'Linux', 'GNU' or 'BSD' when a non-standard API is Linux- or GNU-only or if it's (de-facto) standard in the BSDs. - In some cases content that should go into one of these sections was in NOTES. Move it from there to where it corresponds. - In the SYNOPSIS, I added [[deprecated]] in some functions that I found are deprecated by the relevant standards. - A few other related changes... Cc: Oskari Pirhonen <xxc3ncoredxx@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-21man*/: Replace links to <sources.redhat.com>Yedidyah Bar David3-4/+4
<sources.redhat.com/bugzilla> seems broken right now. Apparently it was replaced, quite a long time ago --based on what I can find on the net-- with <www.sourceware.org/bugzilla>, which does work. This patch was created with: $ find man* -type f \ | xargs grep -l 'sources.redhat.com/bugzilla' \ | xargs sed -i 's;http://sources.redhat.com/bugzilla/;https://www.sourceware.org/bugzilla/;g' Verified with: $ git diff | sed -n 's;^+.*\(https://www.sourceware.org/bugzilla/show_bug.cgi?id=[0-9]*\).*;\1;p' > URLs $ mkdir test $ cd test $ wget -i ../URLs Signed-off-by: Yedidyah Bar David <didi@redhat.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-18man*/: tfixTom Schwindl2-2/+2
Signed-off-by: Tom Schwindl <schwindl@posteo.de> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-17man2/, man3/, man-pages.7: Move VERSIONS next to STANDARDSAlejandro Colomar1-1/+1
VERSIONS and STANDARDS are closely related (and often the distinction is not so clear). Now that we're going to add another section, HISTORY, that is related to both, it makes sense to have the three together. As a curiosity, the list in man-pages(7) that detailed what each section should contain had them by accident(?) in the order that we're moving to, instead of the order that was used elsewhere. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-17feature_test_macros.7: STANDARDS: Some ftm are specific to glibc, not LinuxAlejandro Colomar1-1/+1
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-17inode.7: STANDARDS: Remove bogus recommendationAlejandro Colomar1-12/+0
'blkcnt_t' is defined in <sys/types.h>, per POSIX.1-2001, as blkcnt_t(3type) documents. Also, it doesn't need any ftm(7) to be defined, AFAICS: $ cat blkcnt_t.c #include <sys/types.h> int main(void) { blkcnt_t x; return x = 0; } $ cc -Wall -Wextra blkcnt_t.c $ Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-17capabilities.7: ffixAlejandro Colomar1-1/+2
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-17hier.7: ffixAlejandro Colomar1-2/+3
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-17ip.7: Fix IP_MULTICAST_ALL descriptionChristoph Lameter1-4/+1
INADDR_ANY has nothing to do with the IP_MULTICAST_ALL option. It does not matter if the interface is bound to all interfaces or a particular interface for the functionality of IP_MULTICAST_ALL. Multicast datagrams are addressed to a multicast IP address and will enter the network stack via a particular interface. The application can choose from which interface it will receive multicast data by binding the socket to an IP address. It can then use the IP_MULTICAST_ALL option to restrict the multicast groups that the IP stack will deliver via the socket. Signed-off-by: Christoph Lameter <cl@linux.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-17suffixes.7: ffixAlejandro Colomar1-1/+1
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-17suffixes.7: Add .shtmlAlejandro Colomar1-0/+1
Link: <https://stackoverflow.com/questions/519619/what-is-the-purpose-and-uniqueness-shtml> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-15arc4random.3, man-pages.7: ffixAlejandro Colomar1-1/+1
Reported-by: Jakub Wilk <jwilk@jwilk.net> Cc: Tom Schwindl <schwindl@posteo.de> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-13standards.7: ffixOskari Pirhonen1-1/+1
Fix indentation of the LFS entry. Signed-off-by: Oskari Pirhonen <xxc3ncoredxx@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-12session-keyring.7: ffixAlejandro Colomar1-1/+3
Add a man-page reference at the first occurence of PAM. Reported-by: Helge Kreutzmann <debian@helgefjell.de> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-12charsets.7: „German“ quotations are not old-style, but rather standardAlejandro Colomar1-1/+1
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-12man*/: Fix ISO -> ISO/IEC where appropriateAlejandro Colomar3-11/+11
Link: <https://www.iso.org> Reported-by: Helge Kreutzmann <debian@helgefjell.de> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-12man7/: ffixAlejandro Colomar2-2/+2
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-12boot.7: ffixAlejandro Colomar1-1/+3
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-12boot.7: wfix + ffixAlejandro Colomar1-12/+15
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-12man7/: ffixAlejandro Colomar2-3/+3
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-11standards.7: ffixJakub Wilk1-1/+1
Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-09suffixes.7: Add .jsx and .tsxAlejandro Colomar1-0/+2
Cc: Timo Stark <t.stark@nginx.com> Cc: Andrew Clayton <andrew@digital-domain.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-09man*/: ffixTom Schwindl1-2/+2
Signed-off-by: Tom Schwindl <schwindl@posteo.de> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-08string_copying.7: Modify implementation of stpecpy()Alejandro Colomar1-3/+2
- Don't crash on invalid input. That should be done in a wrapper, if wanted. - Accept NULL as input, since that allows chaining with stpeprintf(). Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-08string_copying.7: srcfix (unmatched RE)Alejandro Colomar1-1/+0
Reported-by: mandoc(1) (make lint-man-mandoc) Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-08man*/: srcfix (IP)Alejandro Colomar2-4/+2
Two consecutive IPs without text don't make sense, since they are paragraph separators. The reason we needed it was that PD 0 was misplaced. This extra IP was also causing another problem: we needed to specify again the indentation of the outer list. Reported-by: mandoc(1) (make lint-man-mandoc) Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-08man*/: ffix (semantic newlines; commas)Alejandro Colomar5-28/+37
Reported-by: mandoc(1) (make lint-man-mandoc) Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-06udp.7: Fix man page reference (section number)Alejandro Colomar1-2/+2
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-06udp.7: add UDP_GROWillem de Bruijn1-0/+14
UDP_GRO was added in commit e20cf8d3f1f7 ("udp: implement GRO for plain UDP sockets.") $ git describe --contains e20cf8d3f1f7 linux/v5.0-rc1~129^2~379^2~8 Kernel source has example code in tools/testing/selftests/net/udpgro* Per https://www.kernel.org/doc/man-pages/patches.html, "Describe how you obtained the information in your patch": I reviewed the relevant UDP_GRO patches. Signed-off-by: Willem de Bruijn <willemb@google.com> Reviewed-by: Simon Horman <simon.horman@corigine.com> Cc: <pabeni@redhat.com> Cc: <netdev@vger.kernel.org> [ alx: srcfix ] Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-06udp.7: add UDP_SEGMENTWillem de Bruijn1-0/+29
UDP_SEGMENT was added in commit bec1f6f69736 ("udp: generate gso with UDP_SEGMENT") $ git describe --contains bec1f6f69736 linux/v4.18-rc1~114^2~377^2~8 Kernel source has example code in tools/testing/selftests/net/udpgso* Per https://www.kernel.org/doc/man-pages/patches.html, "Describe how you obtained the information in your patch": I am the author of the above commit and follow-ons. Signed-off-by: Willem de Bruijn <willemb@google.com> Reviewed-by: Simon Horman <simon.horman@corigine.com> Cc: <pabeni@redhat.com> Cc: <netdev@vger.kernel.org> [ alx: srcfix + use interval notation ] Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-26suffixes.7: Add .js and .ts extensionsAlejandro Colomar1-0/+2
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-25landlock.7: ffixAlejandro Colomar1-1/+1
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-25landlock.7: Move the warning about missing features into the CAVEATS sectionGünther Noack1-1/+1
Putting the warning there makes it more prominent. CAVEATS is a standard section that exists in many man pages and is also described in man-pages(7). Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-10units.7: srcfix (\(mc -> \[mc])G. Branden Robinson1-1/+1
Use correct *roff special character for micro sign. Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-10vdso.7: fix deadlinks to Linux Documentation/наб1-5/+5
Respectively: commit dc7a12bdfccd94c31f79e294f16f7549bd411b49 ("docs: arm: convert docs to ReST and rename to *.rst") commit db9a0975a20c1f21c108b9d44545792d790593e4 ("docs: ia64: convert to ReST") commit e77e9187ae1caf2d83dd5e7f0c1466254b644a4c ("docs: parisc: convert to ReST and add to documentation body") Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-10man*/: srcfix (^ -> \[ha])G. Branden Robinson8-44/+44
Use correct *roff special character for hat/caret/circumflex accent. Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-10sched.7: srcfixG. Branden Robinson1-4/+4
Fix warnings from formatter. troff:./man7/sched.7:989: warning [p 10, 2.7i]: cannot adjust line troff:./man7/sched.7:990: warning [p 10, 2.8i]: cannot adjust line Add hyphenless break points to file names, but also suppress hyphenation to reduce copy-and-paste frustration. Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-08persistent-keyring.7: wfixJakub Wilk1-2/+2
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-06units.7: Add break points in URIAlejandro Colomar1-1/+1
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-06units.7: Fix escapes (\-) in URIAlejandro Colomar1-1/+1
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05units.7: Use \[mc] instead of \(mcAlejandro Colomar1-1/+1
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05prctl.2, man.7: Use \[ga] instead of \(gaAlejandro Colomar1-1/+1
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05Many pages: Use \[bu] instead of \(buAlejandro Colomar35-674/+674
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05Various pages: Use \[rq] instead of \(rqAlejandro Colomar4-8/+8
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05Various pages: Use \[lq] instead of \(lqAlejandro Colomar4-8/+8
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05Many pages: Use \[ha] instead of \(haAlejandro Colomar7-21/+21
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05Many pages: Use \[ti] instead of \(tiAlejandro Colomar12-17/+17
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05Many pages: Use \[em] instead of \(emAlejandro Colomar29-59/+59
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05Many pages: Use \[en] instead of \(enAlejandro Colomar5-15/+15
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05man-pages.7: Recommend using \[..] instead of \(.. escapesAlejandro Colomar1-5/+5
They are more readable. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05Many pages: Use \[dq] instead of \(dqAlejandro Colomar4-44/+44
This improves readability in the source code, since it delimits where the escape sequence ends. Cc: наб <nabijaczleweli@nabijaczleweli.xyz> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Cc: Brian Inglis <Brian.Inglis@Shaw.ca> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05Many pages: Use \[aq] instead of \(aqAlejandro Colomar36-257/+257
This improves readability in the source code, since it delimits where the escape sequence ends. Cc: наб <nabijaczleweli@nabijaczleweli.xyz> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Cc: Brian Inglis <Brian.Inglis@Shaw.ca> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05Many pages: Use lowercase for 'glibc'Alejandro Colomar5-5/+5
It's a proper noun, whose original letter case should be respected. glibc's own documentation uses always lowercase; let's do the same here. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05namespaces.7: ffixAlejandro Colomar1-1/+1
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05charsets.7: wfixAlejandro Colomar1-4/+4
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05landlock.7: tfixGünther Noack1-1/+1
Signed-off-by: Günther Noack <gnoack3000@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05landlock.7: ffixGünther Noack1-1/+2
Signed-off-by: Günther Noack <gnoack3000@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-01vdso.7: Fix risc-v symbol names.Elliott Hughes1-6/+6
The kernel git history says the names have always been "__vdso_" rather than "__kernel_", so I assume this was a copy & paste mistake from a different architecture. Luckily, the path to the kernel source that lets you confirm/deny this _is_ correct :-) Signed-off-by: Elliott Hughes <enh@google.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-01-31bpf-helpers.7: Refresh pageAlejandro Colomar1-59/+376
See commit 19c7f78393f2 ("bpf-helpers.7: Refresh page") Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-01-29charsets.7: wfixAlejandro Colomar1-1/+1
Several of the languages mentioned are not West Europe. Some come from the North, South, or East. Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Cc: Stefan Puiu <stefan.puiu@gmail.com> Cc: Bernd Petrovitsch <bernd@petrovitsch.priv.at> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-01-22Various pages: wfixAlejandro Colomar2-6/+8
Fixes: b324e17d3208 ("Many pages: wfix") Reported-by: Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-01-22user_namespaces.7: ffixAlejandro Colomar1-5/+5
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-01-22session-keyring.7: SEE ALSO: refer to PAM(7)Alejandro Colomar1-0/+1
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-01-22socket.7: tfixJan Engelhardt2-8/+8
The .TP macro is followed by exactly one line of definition, and then multiple lines of flowed explanatory text. When flowed, the lack of periods is apparent in sentences. Signed-off-by: Jan Engelhardt <jengelh@inai.de> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-01-15units.7: Remove references to NISTAlejandro Colomar1-11/+0
The SI brochure is the reference. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-01-15units.7: Add decimal and binary prefixesAlejandro Colomar1-0/+6
The SI added prefixes for 10^(+-)27 and 30 in 2022. While updating this, I realized that we were missing Zi and Yi, which are specified by the SI, I guess since a long time ago. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-01-07libc.7: ffixG. Branden Robinson1-5/+6
* Use typographer's quotation marks instead of '"' for quotation. * Hyperlink the text "GNU C Library" to its website. Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-01-07Many pages: TH: Use lowercaseAlejandro Colomar5-5/+5
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-01-07libc.7: srcfixG. Branden Robinson1-14/+26
* Set multi-word parentheticals on their own input lines. * Break input lines after commas. * Add hyphenless break points to URLs. Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-01-02man-pages.7: Add preferred term "symbolic link".G. Branden Robinson1-0/+1
...per discussion with Alex Colomar. Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-01-02path_resolution.7: wfixG. Branden Robinson1-5/+7
Not counting function names and cross references to the symlink(7) page, "symbolic link" is preferred to "symlink" in existing pages by a ratio of about 380 to the handful in this page. Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-30bpf-helpers.7, open_how.2type, string_copying.7: tfixSamanta Navarro2-4/+4
Typos found with codespell. Signed-off-by: Samanta Navarro <ferivoz@riseup.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-28charsets.7: tfixLennart Jablonka1-1/+1
Signed-off-by: Lennart Jablonka <humm@ljabl.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-24string_copying.7: Remove stpecpyx()Alejandro Colomar1-49/+16
And give stpecpy() with the semantics of stpecpyx(). Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-22string_copying.7: tfixAlejandro Colomar1-1/+1
Reported-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>