aboutsummaryrefslogtreecommitdiffstats
path: root/man7
AgeCommit message (Collapse)AuthorFilesLines
2022-12-20string_copying.7: tfixAlejandro Colomar1-1/+1
Reported-by: Stefan Puiu <stefan.puiu@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-20suffixes.7: Improve table formatG. Branden Robinson1-216/+216
Apparently the original author(s) of this table did not know how to start a table entry in the first column of a tbl(1) table with a dot. (If you try, the *roff formatter will interpret it as a control line, and try to invoke a request or call a macro.) Start every row of the table with the *roff dummy character `\&` instead of leading space. Not only is this more idiomatic, but it recovers some of the line length for content. This patch does not attempt to correct any errors in the table contents, nor bring it up to date from its year 2000 vintage. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-20suffixes.7: Drop diagnostic-suppressing hackG. Branden Robinson1-3/+0
The extension of the page length is workaround for <https://savannah.gnu.org/bugs/?63449>, which is a very old groff bug, possibily dating back to groff 1.00 or beyond. It is fixed in groff Git. But waiting for a groff release is not necessary; man-db man(1) nowadays conceals diagnostic messages from the formatter and output drivers. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-20string_copying.7: Add page to document all string-copying functionsAlejandro Colomar1-0/+855
This is an opportunity to use consistent language across the documentation for all string-copying functions. It is also easier to show the similarities and differences between all of the functions, so that a reader can use this page to know which function is needed for a given task. Alternative functions not provided by libc have been given in the same page, with reference implementations. Cc: Martin Sebor <msebor@redhat.com> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Cc: Douglas McIlroy <douglas.mcilroy@dartmouth.edu> Cc: Jakub Wilk <jwilk@jwilk.net> Cc: Serge Hallyn <serge@hallyn.com> Cc: Iker Pedrosa <ipedrosa@redhat.com> Cc: Andrew Pinski <pinskia@gmail.com> Cc: Stefan Puiu <stefan.puiu@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-15Many pages: Add '\" t' comment where necessaryAlejandro Colomar42-0/+42
Scripted change: $ grep -l -x '^[.]TS$' man*/* | sort -u | xargs sed -i -e "1i'\\\\\" t" Link: <https://lore.kernel.org/linux-man/07a7d4e7-79a6-b2c3-6892-1e39a0679f27@gmail.com/T/#mcf36c8a387fd5ff4f800dc220e3dbdd229b556bd> Reported-by: Jakub Wilk <jwilk@jwilk.net> Cc: Mike Frysinger <vapier@gentoo.org> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Cc: Michael Kerrisk <mtk.manpages@gmail.com> Cc: Stefan Puiu <stefan.puiu@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-15man-pages.7: tfixEric Biggers1-4/+4
Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-11socket.7: Be explicit that accept(2) respects SO_*TIMEOAlejandro Colomar1-0/+1
See the previous commit. Reported-by: Luis Javier Merino <ninjalj@gmail.com> Cc: Tycho Andersen <tycho@tycho.pizza> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-09socket.7: be explicit that connect(2) respects SO_*TIMEOTycho Andersen1-0/+1
Our group recently had some confusion around this. Although f327722042df ("socket.7: Explain effect of SO_SNDTIMEO for connect()") adds a mention of connect(2), the wording around "Timeouts only have effect for system calls that perform socket I/O" is slightly confusing: is connect(2) I/O?. Let's just add connect(2) to the list of things that time out explicitly to avoid any confusion. Test program for grins: #include <stdio.h> #include <sys/socket.h> #include <netinet/ip.h> #include <arpa/inet.h> int main(void) { struct sockaddr_in servaddr = { /* tycho.pizza */ .sin_addr.s_addr = inet_addr("192.241.255.151"), .sin_port = htons(443), .sin_family = AF_INET, }; int fd; struct timeval timeout = { .tv_sec = 0, .tv_usec = 100, }; fd = socket(AF_INET, SOCK_STREAM, 0); if (fd < 0) { perror("socket"); return 1; } if (setsockopt(fd, SOL_SOCKET, SO_SNDTIMEO, &timeout, sizeof(timeout)) < 0) { perror("setsockopt"); return 1; } if (connect(fd, (struct sockaddr *)&servaddr, sizeof(servaddr)) < 0) { perror("connect"); return 1; } printf("connect successful\n"); return 0; } $ ./so_sndtimeo connect: Operation now in progress Signed-off-by: Tycho Andersen <tycho@tycho.pizza> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-04path_resolution.7: ffixAlejandro Colomar1-1/+3
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blättermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-04credentials.7: tfixAlejandro Colomar1-1/+1
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blättermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-04credentials.7: tfixAlejandro Colomar1-1/+1
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blättermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-04uts_namespaces.7: wfixAlejandro Colomar1-1/+1
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blättermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-04user_namespaces.7: Add missing wordAlejandro Colomar1-2/+2
Cc: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blättermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-04user_namespaces.7: ffixAlejandro Colomar1-1/+1
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blättermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-04user_namespaces.7: wfixAlejandro Colomar1-2/+2
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blättermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-04time_namespaces.7: tfixAlejandro Colomar1-1/+1
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blättermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-04Many pages: wfixAlejandro Colomar34-235/+233
Refer consistently to software versions. In most cases, it is done as <software> <version>. In the case of Linux and glibc, use the project name, instead of other terms such as 'kernel' or 'library'. I found the uses of inconsistent language with the following: $ find man* -type f \ | xargs grep -i '\(since\|before\|after\|until\|to\|from\|in\|between\|version\|with\) \(kernel\|version\|2\.\|3\.\|4\.\|5\.\)' \ | sort However, I might have missed some cases. Anyway, 99% consistency is pretty good consistency. We'll fix the remaining cases as we see them. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-04network_namespaces.7: wfixAlejandro Colomar1-1/+2
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blättermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-04mount_namespaces.7: tfixAlejandro Colomar1-1/+1
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blättermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-04mount_namespaces.7: ffixAlejandro Colomar1-16/+62
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blättermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-04mount_namespaces.7: tfixAlejandro Colomar1-1/+1
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blättermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-04keyrings.7: wfixAlejandro Colomar1-1/+1
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blättermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-11-22sendfile.2, vfork.2, alloca.3, getcontext.3, tmpfs.5, ttytype.5, spufs.7: ffixAlejandro Colomar1-2/+4
Break lines containing two man page references into a line for each. This is not only more consistent with our guidelines (man-pages(7)); it also helps prepare for the future adoption of the MR man(7) macro. Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-11-01keyrings.7: tfix hexadecimal number prefixGrzegorz Szymaszek1-1/+1
In the DESCRIPTION, where the Permissions column of /proc/keys is explained, the 0x02 value was written as Ox02. In case one cannot spot the difference: the first character was letter o (U+004F), while it should be digit zero (U+0030). It seems the source tree does not contain any other "Ox" instances except at the beginning of "Oxford". Signed-off-by: Grzegorz Szymaszek <gszymaszek@short.pl> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-30get_nprocs.3, get_nprocs_conf.3, program_invocation_name.3, sysvipc.7: Match ↵Alejandro Colomar1-1/+1
page title with file name and NAME section Manually tweak a few pages that weren't covered by the scripts used in the 2 previous commits. On 10/30/22 23:00, G. Branden Robinson wrote: > For those to whom this change is coming as an unpleasant surprise, the > forthcoming groff 1.23.0 features an option that will reverse this > change at rendering time. > > From groff_man(7): > > -rCT=1 Capitalize titles, setting the man page title (the first > argument to .TH) in full capitals in headers and footers. > This transformation is off by default because it discards > case distinction information. > > This register can also be set in a site-local "man.local" file to force > it on for all pages. On Debian-based systems, this file is in > /etc/groff. The following line will do the trick. > > .nr CT 1 > > The groff_man_style(7) man page offers further examples of such > rendering customization. > > /usr/local/share/groff/site-tmac/man.local > Put site‐local changes and customizations into this file. > > .\" Use narrower indentation on terminals and similar. > .if n .nr IN 4n > .\" Put only one space after the end of a sentence. > .ss 12 0 \" See groff(7). > .\" Keep pages narrow even on wide terminals. > .if n .if \n[LL]>78n .nr LL 78n > .\" Ensure hyperlinks are enabled for terminals. > .nr U 1 > > On multi‐user systems, it is more considerate to users whose > preferences may differ from the administrator’s to be less > aggressive with such settings, or to permit their override > with a user‐specific man.local file. This can be achieved by > placing one or both of following requests at the end of the > site‐local file. > .soquiet \V[XDG_CONFIG_HOME]/man.local > .soquiet \V[HOME]/.man.local > However, a security‐sandboxed man(1) program may lack > permission to open such files. Cc: Ingo Schwarze <schwarze@openbsd.org> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-30Various pages: Use correct letter case in page titles (TH)Alejandro Colomar8-8/+8
Semi-scripted change: $ find man* -type f \ | xargs grep -L '\.so' \ | while read f; do P=$(basename $f); T=$(grep '\.TH ' $f | cut -f2,3 -d' ' | sed 's/ /./'); p=$(echo $P | tr '[:upper:]' '[:lower:]'); t=$(echo $T | tr '[:upper:]' '[:lower:]'); Tn=$(echo $T | sed 's/\.[^.]\+$//') Pn=$(echo $P | sed 's/\.[^.]\+$//') N=$(man_section $f NAME \ | sed -n '/NAME/,/ - /p' \ | sed 's/ - .*//' \ | grep -v '^NAME$' \ | tr ', ' '\n' \ | grep -i "^$Pn$" \ | head -n1) test $P = $T \ && test -n $N \ && continue; if test "x$p" != "x$t"; then echo 1 $P $T $N; elif test -z "$N"; then sed -i "/\.TH /s/$Tn/$Pn/" $f; fi; done; Most of the changes produced by this script needed to be reverted, but the some of them were good. On 10/30/22 23:00, G. Branden Robinson wrote: > For those to whom this change is coming as an unpleasant surprise, the > forthcoming groff 1.23.0 features an option that will reverse this > change at rendering time. > > From groff_man(7): > > -rCT=1 Capitalize titles, setting the man page title (the first > argument to .TH) in full capitals in headers and footers. > This transformation is off by default because it discards > case distinction information. > > This register can also be set in a site-local "man.local" file to force > it on for all pages. On Debian-based systems, this file is in > /etc/groff. The following line will do the trick. > > .nr CT 1 > > The groff_man_style(7) man page offers further examples of such > rendering customization. > > /usr/local/share/groff/site-tmac/man.local > Put site‐local changes and customizations into this file. > > .\" Use narrower indentation on terminals and similar. > .if n .nr IN 4n > .\" Put only one space after the end of a sentence. > .ss 12 0 \" See groff(7). > .\" Keep pages narrow even on wide terminals. > .if n .if \n[LL]>78n .nr LL 78n > .\" Ensure hyperlinks are enabled for terminals. > .nr U 1 > > On multi‐user systems, it is more considerate to users whose > preferences may differ from the administrator’s to be less > aggressive with such settings, or to permit their override > with a user‐specific man.local file. This can be achieved by > placing one or both of following requests at the end of the > site‐local file. > .soquiet \V[XDG_CONFIG_HOME]/man.local > .soquiet \V[HOME]/.man.local > However, a security‐sandboxed man(1) program may lack > permission to open such files. Cc: Ingo Schwarze <schwarze@openbsd.org> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-30Many pages: Use correct letter case in page titles (TH)Alejandro Colomar83-83/+83
Scripted change: $ find man* -type f \ | xargs grep -L '\.so' \ | while read f; do P=$(basename $f); T=$(grep '\.TH ' $f | cut -f2,3 -d' ' | sed 's/ /./'); p=$(echo $P | tr '[:upper:]' '[:lower:]'); t=$(echo $T | tr '[:upper:]' '[:lower:]'); Tn=$(echo $T | sed 's/\.[^.]\+$//') Pn=$(echo $P | sed 's/\.[^.]\+$//') N=$(man_section $f NAME \ | sed -n '/NAME/,/ - /p' \ | sed 's/ - .*//' \ | grep -v '^NAME$' \ | tr ', ' '\n' \ | grep -i "^$Pn$" \ | head -n1) test $P = $T \ && test -n $N \ && continue; if test "x$p" != "x$t"; then echo 1 $P $T $N; elif test -z "$N"; then echo 2 $P $T $N; else sed -i "/\.TH /s/$Tn/$N/" $f; fi; done; On 10/30/22 23:00, G. Branden Robinson wrote: > For those to whom this change is coming as an unpleasant surprise, the > forthcoming groff 1.23.0 features an option that will reverse this > change at rendering time. > > From groff_man(7): > > -rCT=1 Capitalize titles, setting the man page title (the first > argument to .TH) in full capitals in headers and footers. > This transformation is off by default because it discards > case distinction information. > > This register can also be set in a site-local "man.local" file to force > it on for all pages. On Debian-based systems, this file is in > /etc/groff. The following line will do the trick. > > .nr CT 1 > > The groff_man_style(7) man page offers further examples of such > rendering customization. > > /usr/local/share/groff/site-tmac/man.local > Put site‐local changes and customizations into this file. > > .\" Use narrower indentation on terminals and similar. > .if n .nr IN 4n > .\" Put only one space after the end of a sentence. > .ss 12 0 \" See groff(7). > .\" Keep pages narrow even on wide terminals. > .if n .if \n[LL]>78n .nr LL 78n > .\" Ensure hyperlinks are enabled for terminals. > .nr U 1 > > On multi‐user systems, it is more considerate to users whose > preferences may differ from the administrator’s to be less > aggressive with such settings, or to permit their override > with a user‐specific man.local file. This can be achieved by > placing one or both of following requests at the end of the > site‐local file. > .soquiet \V[XDG_CONFIG_HOME]/man.local > .soquiet \V[HOME]/.man.local > However, a security‐sandboxed man(1) program may lack > permission to open such files. Cc: Ingo Schwarze <schwarze@openbsd.org> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-30Change alx's email addressAlejandro Colomar2-2/+2
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-29man-pages.7: Document how to write listsAlejandro Colomar1-0/+58
Reported-by: Mike Frysinger <vapier@gentoo.org> Acked-by: Douglas McIlroy <douglas.mcilroy@dartmouth.edu> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-29Many pages: Use a consistent style for listsAlejandro Colomar36-601/+602
There are different kinds of lists: Tagged paragraphs These are fixed in a separate commit (the previous one). They are used for a list of tags and their descriptions. An example is this commit message itself. Ordered lists Elements are preceeded by a number in parentheses. These represent a set of steps that have an order. When there are substeps, they will be numbered like (4.2). Positional lists Elements are preceeded by a number in square brackets (index). These represent fields in a set. The index will start at: 0 fields of a C data structure, to be consistent with arrays. 1 fields of a file, to be consistent with tools like cut(1). Alternatives list Elements are preceeded by a letter in parentheses. These represent a set of (normally) exclusive alternatives. Bullet lists Elements are preceeded by bullet symbols. Anything that doesn't fit elsewhere usually is covered by this type of list. Notes Not really a list, but the syntax is identical to "positional lists". There should always be 2 spaces between the list symbol and the elements. This doesn't apply to "tagged paragraphs", which use the default indentation rules. Reported-by: Mike Frysinger <vapier@gentoo.org> Cc: <groff@gnu.org> Acked-by: Douglas McIlroy <douglas.mcilroy@dartmouth.edu> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-29Many pages: Use .TP for tagged paragraphsAlejandro Colomar10-82/+148
Reported-by: Mike Frysinger <vapier@gentoo.org> Cc: <groff@gnu.org> Acked-by: Douglas McIlroy <douglas.mcilroy@dartmouth.edu> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-25ascii.7: Chase down History to earliestнаб1-3/+1
Cf., well, the UNIX Programmer's Manual: https://www.tuhs.org/Archive/Distributions/Research/Dennis_v1/UNIX_ProgrammersManual_Nov71.pdf PDF page 191; yes, the typographical convention here is insane, and the contemprary-correct way to refer to this page from within the manual would be /just/ "/etc/ascii", but, given the context, "/etc/ascii (VII)" makes the most sense to me Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-23capabilities.7: ffixAlejandro Colomar1-1/+1
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-23cpuset.7: tfixAlejandro Colomar1-1/+1
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-23locale.7: srcfixAlejandro Colomar1-1/+1
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-23man-pages.7: ffixAlejandro Colomar1-15/+17
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-22man-pages.7: Use . consistently in bulleted listMike Frysinger1-1/+1
Signed-off-by: Mike Frysinger <vapier@gentoo.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-22man-pages.7: Add missing . before macroMike Frysinger1-1/+1
Signed-off-by: Mike Frysinger <vapier@gentoo.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-14feature_test_macros.7: document _TIME_BITS (time64)Sam James1-0/+15
Some notes: * glibc is the only libc I'm aware of implementing _TIME_BITS for time64 compatibility. It was introduced in glibc-2.34; * musl libc made a hard switch in 1.2.0, see https://musl.libc.org/time64.html; * Using _TIME_BITS=64 with glibc requires _FILE_OFFSET_BITS=64 (which is used for Large File Support)! Extraordinary claims require (some) evidence, so see https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/unix/sysv/linux/features-time64.h;h=84d56ee3ff2ecfa0d2499385623f30606f84a1bf. Reference: https://wiki.gentoo.org/wiki/Project:Toolchain/time64_migration Reference: https://sourceware.org/pipermail/libc-alpha/2022-January/134985.html Signed-off-by: Sam James <sam@gentoo.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-14feature_test_macros.7: document -D_FORTIFY_SOURCE=3Sam James1-0/+16
Reference: https://developers.redhat.com/blog/2021/04/16/broadening-compiler-checks-for-buffer-overflows-in-_fortify_source Reference: https://developers.redhat.com/articles/2022/09/17/gccs-new-fortification-level Signed-off-by: Sam James <sam@gentoo.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-09dist.mk, All pages: .TH: Generate date at 'make dist'Alejandro Colomar120-120/+120
Replace the date by a placeholder (date) in the repo, as we're doing with the version (unreleased). It will be filled when the tarball is generated with 'make dist' (or equivalent) with the date of the most recent git commit that modifies the page (as was done previously by update_timestamps.sh, which has been removed). Scripted change (mostly): $ find man* -type f \ | xargs sed -Ei '/^\.TH /s/.TH +([^ ]+ +[^ ]+) +[^ ]+ +(.*)/.TH \1 (date) \2/' Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-11hier.7: tfixAlejandro Colomar1-1/+1
Reported-by: Grigoriy <grigoriyremvar@protonmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-09getent.1, iconv.1, intro.1, ldd.1, locale.1, localedef.1, memusage.1, ↵Alejandro Colomar121-121/+121
memusagestat.1, mtrace.1, pldd.1, sprof.1, time.1, _exit.2, _syscall.2, accept.2, access.2, acct.2, add_key.2, adjtimex.2, alarm.2, alloc_hugepages.2, arch_prctl.2, bdflush.2, bind.2, bpf.2, brk.2, cacheflush.2, capget.2, chdir.2, chmod.2, chown.2, chroot.2, clock_getres.2, clock_nanosleep.2, clone.2, close.2, close_range.2, connect.2, copy_file_range.2, create_module.2, delete_module.2, dup.2, epoll_create.2, epoll_ctl.2, epoll_wait.2, eventfd.2, execve.2, execveat.2, exit_group.2, fallocate.2, fanotify_init.2, fanotify_mark.2, fcntl.2, flock.2, fork.2, fsync.2, futex.2, futimesat.2, get_kernel_syms.2, get_mempolicy.2, get_robust_list.2, getcpu.2, getdents.2, getdomainname.2, getgid.2, getgroups.2, gethostname.2, getitimer.2, getpagesize.2, getpeername.2, getpid.2, getpriority.2, getrandom.2, getresuid.2, getrlimit.2, getrusage.2, getsid.2, getsockname.2, getsockopt.2, gettid.2, gettimeofday.2, getuid.2, getunwind.2, getxattr.2, idle.2, init_module.2, inotify_add_watch.2, inotify_init.2, inotify_rm_watch.2, intro.2, io_cancel.2, io_destroy.2, io_getevents.2, io_setup.2, io_submit.2, ioctl.2, ioctl_console.2, ioctl_fat.2, ioctl_ficlonerange.2, ioctl_fideduperange.2, ioctl_fslabel.2, ioctl_getfsmap.2, ioctl_iflags.2, ioctl_ns.2, ioctl_tty.2, ioctl_userfaultfd.2, ioperm.2, iopl.2, ioprio_set.2, ipc.2, kcmp.2, kexec_load.2, keyctl.2, kill.2, landlock_add_rule.2, landlock_create_ruleset.2, landlock_restrict_self.2, link.2, listen.2, listxattr.2, llseek.2, lookup_dcookie.2, lseek.2, madvise.2, mbind.2, membarrier.2, memfd_create.2, memfd_secret.2, migrate_pages.2, mincore.2, mkdir.2, mknod.2, mlock.2, mmap.2, mmap2.2, modify_ldt.2, mount.2, mount_setattr.2, move_pages.2, mprotect.2, mq_getsetattr.2, mremap.2, msgctl.2, msgget.2, msgop.2, msync.2, nanosleep.2, nfsservctl.2, nice.2, open.2, open_by_handle_at.2, openat2.2, outb.2, pause.2, pciconfig_read.2, perf_event_open.2, perfmonctl.2, personality.2, pidfd_getfd.2, pidfd_open.2, pidfd_send_signal.2, pipe.2, pivot_root.2, pkey_alloc.2, poll.2, posix_fadvise.2, prctl.2, pread.2, process_madvise.2, process_vm_readv.2, ptrace.2, query_module.2, quotactl.2, read.2, readahead.2, readdir.2, readlink.2, readv.2, reboot.2, recv.2, recvmmsg.2, remap_file_pages.2, removexattr.2, rename.2, request_key.2, restart_syscall.2, rmdir.2, rt_sigqueueinfo.2, s390_guarded_storage.2, s390_pci_mmio_write.2, s390_runtime_instr.2, s390_sthyi.2, sched_get_priority_max.2, sched_rr_get_interval.2, sched_setaffinity.2, sched_setattr.2, sched_setparam.2, sched_setscheduler.2, sched_yield.2, seccomp.2, seccomp_unotify.2, select.2, select_tut.2, semctl.2, semget.2, semop.2, send.2, sendfile.2, sendmmsg.2, set_mempolicy.2, set_thread_area.2, set_tid_address.2, seteuid.2, setfsgid.2, setfsuid.2, setgid.2, setns.2, setpgid.2, setresuid.2, setreuid.2, setsid.2, setuid.2, setup.2, setxattr.2, sgetmask.2, shmctl.2, shmget.2, shmop.2, shutdown.2, sigaction.2, sigaltstack.2, signal.2, signalfd.2, sigpending.2, sigprocmask.2, sigreturn.2, sigsuspend.2, sigwaitinfo.2, socket.2, socketcall.2, socketpair.2, splice.2, spu_create.2, spu_run.2, stat.2, statfs.2, statx.2, stime.2, subpage_prot.2, swapon.2, symlink.2, sync.2, sync_file_range.2, syscall.2, syscalls.2, sysctl.2, sysfs.2, sysinfo.2, syslog.2, tee.2, time.2, timer_create.2, timer_delete.2, timer_getoverrun.2, timer_settime.2, timerfd_create.2, times.2, tkill.2, truncate.2, umask.2, umount.2, uname.2, unimplemented.2, unlink.2, unshare.2, uselib.2, userfaultfd.2, ustat.2, utime.2, utimensat.2, vfork.2, vhangup.2, vm86.2, vmsplice.2, wait.2, wait4.2, write.2, open_how.2type, CPU_SET.3, FILE.3, INFINITY.3, MAX.3, MB_CUR_MAX.3, MB_LEN_MAX.3, _Generic.3, __ppc_get_timebase.3, __ppc_set_ppr_med.3, __ppc_yield.3, __setfpucw.3, a64l.3, abort.3, abs.3, acos.3, acosh.3, addseverity.3, adjtime.3, aio_cancel.3, aio_error.3, aio_fsync.3, aio_init.3, aio_read.3, aio_return.3, aio_suspend.3, aio_write.3, alloca.3, argz_add.3, asin.3, asinh.3, asprintf.3, assert.3, assert_perror.3, atan.3, atan2.3, atanh.3, atexit.3, atof.3, atoi.3, backtrace.3, basename.3, bcmp.3, bcopy.3, bindresvport.3, bsd_signal.3, bsearch.3, bstring.3, bswap.3, btowc.3, btree.3, byteorder.3, bzero.3, cabs.3, cacos.3, cacosh.3, canonicalize_file_name.3, carg.3, casin.3, casinh.3, catan.3, catanh.3, catgets.3, catopen.3, cbrt.3, ccos.3, ccosh.3, ceil.3, cexp.3, cexp2.3, cfree.3, cimag.3, circleq.3, clearenv.3, clock.3, clock_getcpuclockid.3, clog.3, clog10.3, clog2.3, closedir.3, cmsg.3, confstr.3, conj.3, copysign.3, cos.3, cosh.3, cpow.3, cproj.3, creal.3, crypt.3, csin.3, csinh.3, csqrt.3, ctan.3, ctanh.3, ctermid.3, ctime.3, daemon.3, dbopen.3, des_crypt.3, difftime.3, dirfd.3, div.3, dl_iterate_phdr.3, dladdr.3, dlerror.3, dlinfo.3, dlopen.3, dlsym.3, drand48.3, drand48_r.3, duplocale.3, dysize.3, ecvt.3, ecvt_r.3, encrypt.3, end.3, endian.3, envz_add.3, erf.3, erfc.3, err.3, errno.3, error.3, ether_aton.3, euidaccess.3, exec.3, exit.3, exp.3, exp10.3, exp2.3, expm1.3, fabs.3, fclose.3, fcloseall.3, fdim.3, fenv.3, ferror.3, fexecve.3, fflush.3, ffs.3, fgetc.3, fgetgrent.3, fgetpwent.3, fgetwc.3, fgetws.3, fileno.3, finite.3, flockfile.3, floor.3, fma.3, fmax.3, fmemopen.3, fmin.3, fmod.3, fmtmsg.3, fnmatch.3, fopen.3, fopencookie.3, fpathconf.3, fpclassify.3, fpurge.3, fputwc.3, fputws.3, fread.3, frexp.3, fseek.3, fseeko.3, ftime.3, ftok.3, fts.3, ftw.3, futimes.3, fwide.3, gamma.3, gcvt.3, get_nprocs_conf.3, get_phys_pages.3, getaddrinfo.3, getaddrinfo_a.3, getauxval.3, getcontext.3, getcwd.3, getdate.3, getdirentries.3, getdtablesize.3, getentropy.3, getenv.3, getfsent.3, getgrent.3, getgrent_r.3, getgrnam.3, getgrouplist.3, gethostbyname.3, gethostid.3, getifaddrs.3, getipnodebyname.3, getline.3, getloadavg.3, getlogin.3, getmntent.3, getnameinfo.3, getnetent.3, getnetent_r.3, getopt.3, getpass.3, getprotoent.3, getprotoent_r.3, getpt.3, getpw.3, getpwent.3, getpwent_r.3, getpwnam.3, getrpcent.3, getrpcent_r.3, getrpcport.3, gets.3, getservent.3, getservent_r.3, getspnam.3, getsubopt.3, getttyent.3, getusershell.3, getutent.3, getutmp.3, getw.3, getwchar.3, glob.3, gnu_get_libc_version.3, grantpt.3, group_member.3, gsignal.3, hash.3, hsearch.3, hypot.3, iconv.3, iconv_close.3, iconv_open.3, if_nameindex.3, if_nametoindex.3, ilogb.3, index.3, inet.3, inet_net_pton.3, inet_ntop.3, inet_pton.3, initgroups.3, insque.3, intro.3, isalpha.3, isatty.3, isfdtype.3, isgreater.3, iswalnum.3, iswalpha.3, iswblank.3, iswcntrl.3, iswctype.3, iswdigit.3, iswgraph.3, iswlower.3, iswprint.3, iswpunct.3, iswspace.3, iswupper.3, iswxdigit.3, j0.3, key_setsecret.3, killpg.3, ldexp.3, lgamma.3, lio_listio.3, list.3, localeconv.3, lockf.3, log.3, log10.3, log1p.3, log2.3, logb.3, login.3, lrint.3, lround.3, lsearch.3, lseek64.3, makecontext.3, makedev.3, mallinfo.3, malloc.3, malloc_get_state.3, malloc_hook.3, malloc_info.3, malloc_stats.3, malloc_trim.3, malloc_usable_size.3, mallopt.3, matherr.3, mblen.3, mbrlen.3, mbrtowc.3, mbsinit.3, mbsnrtowcs.3, mbsrtowcs.3, mbstowcs.3, mbtowc.3, mcheck.3, memccpy.3, memchr.3, memcmp.3, memcpy.3, memfrob.3, memmem.3, memmove.3, mempcpy.3, memset.3, mkdtemp.3, mkfifo.3, mkstemp.3, mktemp.3, modf.3, mpool.3, mq_close.3, mq_getattr.3, mq_notify.3, mq_open.3, mq_receive.3, mq_send.3, mq_unlink.3, mtrace.3, nan.3, netlink.3, newlocale.3, nextafter.3, nextup.3, nl_langinfo.3, ntp_gettime.3, offsetof.3, on_exit.3, open_memstream.3, opendir.3, openpty.3, perror.3, popen.3, posix_fallocate.3, posix_madvise.3, posix_memalign.3, posix_openpt.3, posix_spawn.3, pow.3, pow10.3, printf.3, profil.3, program_invocation_name.3, psignal.3, pthread_atfork.3, pthread_attr_init.3, pthread_attr_setaffinity_np.3, pthread_attr_setdetachstate.3, pthread_attr_setguardsize.3, pthread_attr_setinheritsched.3, pthread_attr_setschedparam.3, pthread_attr_setschedpolicy.3, pthread_attr_setscope.3, pthread_attr_setsigmask_np.3, pthread_attr_setstack.3, pthread_attr_setstackaddr.3, pthread_attr_setstacksize.3, pthread_cancel.3, pthread_cleanup_push.3, pthread_cleanup_push_defer_np.3, pthread_create.3, pthread_detach.3, pthread_equal.3, pthread_exit.3, pthread_getattr_default_np.3, pthread_getattr_np.3, pthread_getcpuclockid.3, pthread_join.3, pthread_kill.3, pthread_kill_other_threads_np.3, pthread_mutex_consistent.3, pthread_mutexattr_getpshared.3, pthread_mutexattr_init.3, pthread_mutexattr_setrobust.3, pthread_rwlockattr_setkind_np.3, pthread_self.3, pthread_setaffinity_np.3, pthread_setcancelstate.3, pthread_setconcurrency.3, pthread_setname_np.3, pthread_setschedparam.3, pthread_setschedprio.3, pthread_sigmask.3, pthread_sigqueue.3, pthread_spin_init.3, pthread_spin_lock.3, pthread_testcancel.3, pthread_tryjoin_np.3, pthread_yield.3, ptsname.3, putenv.3, putgrent.3, putpwent.3, puts.3, putwchar.3, qecvt.3, qsort.3, raise.3, rand.3, random.3, random_r.3, rcmd.3, re_comp.3, readdir.3, readdir_r.3, realpath.3, recno.3, regex.3, remainder.3, remove.3, remquo.3, resolver.3, rewinddir.3, rexec.3, rint.3, round.3, rpc.3, rpmatch.3, rtime.3, rtnetlink.3, scalb.3, scalbln.3, scandir.3, scanf.3, sched_getcpu.3, seekdir.3, sem_close.3, sem_destroy.3, sem_getvalue.3, sem_init.3, sem_open.3, sem_post.3, sem_unlink.3, sem_wait.3, setaliasent.3, setbuf.3, setenv.3, setjmp.3, setlocale.3, setlogmask.3, setnetgrent.3, shm_open.3, siginterrupt.3, signbit.3, significand.3, sigpause.3, sigqueue.3, sigset.3, sigsetops.3, sigvec.3, sigwait.3, sin.3, sincos.3, sinh.3, sleep.3, slist.3, sockatmark.3, sqrt.3, stailq.3, statvfs.3, stdarg.3, stdin.3, stdio.3, stdio_ext.3, stpcpy.3, stpncpy.3, strcasecmp.3, strcat.3, strchr.3, strcmp.3, strcoll.3, strcpy.3, strdup.3, strerror.3, strfmon.3, strfromd.3, strfry.3, strftime.3, string.3, strlen.3, strnlen.3, strpbrk.3, strptime.3, strsep.3, strsignal.3, strspn.3, strstr.3, strtod.3, strtoimax.3, strtok.3, strtol.3, strtoul.3, strverscmp.3, strxfrm.3, swab.3, sysconf.3, syslog.3, system.3, sysv_signal.3, tailq.3, tan.3, tanh.3, tcgetpgrp.3, tcgetsid.3, telldir.3, tempnam.3, termios.3, tgamma.3, timegm.3, timeradd.3, tmpfile.3, tmpnam.3, toascii.3, toupper.3, towctrans.3, towlower.3, towupper.3, trunc.3, tsearch.3, ttyname.3, ttyslot.3, tzset.3, ualarm.3, ulimit.3, undocumented.3, ungetwc.3, unlocked_stdio.3, unlockpt.3, updwtmp.3, uselocale.3, usleep.3, wcpcpy.3, wcpncpy.3, wcrtomb.3, wcscasecmp.3, wcscat.3, wcschr.3, wcscmp.3, wcscpy.3, wcscspn.3, wcsdup.3, wcslen.3, wcsncasecmp.3, wcsncat.3, wcsncmp.3, wcsncpy.3, wcsnlen.3, wcsnrtombs.3, wcspbrk.3, wcsrchr.3, wcsrtombs.3, wcsspn.3, wcsstr.3, wcstoimax.3, wcstok.3, wcstombs.3, wcswidth.3, wctob.3, wctomb.3, wctrans.3, wctype.3, wcwidth.3, wmemchr.3, wmemcmp.3, wmemcpy.3, wmemmove.3, wmemset.3, wordexp.3, wprintf.3, xcrypt.3, xdr.3, y0.3, NULL.3const, sysexits.h.3head, aiocb.3type, blkcnt_t.3type, blksize_t.3type, cc_t.3type, clock_t.3type, clockid_t.3type, dev_t.3type, div_t.3type, double_t.3type, epoll_event.3type, fenv_t.3type, id_t.3type, intN_t.3type, intmax_t.3type, intptr_t.3type, iovec.3type, itimerspec.3type, lconv.3type, mode_t.3type, off_t.3type, ptrdiff_t.3type, regex_t.3type, size_t.3type, sockaddr.3type, stat.3type, time_t.3type, timer_t.3type, timespec.3type, timeval.3type, tm.3type, va_list.3type, void.3type, cciss.4, console_codes.4, cpuid.4, dsp56k.4, fd.4, full.4, fuse.4, hd.4, hpsa.4, initrd.4, intro.4, lirc.4, loop.4, lp.4, mem.4, mouse.4, msr.4, null.4, pts.4, ram.4, random.4, rtc.4, sd.4, sk98lin.4, smartpqi.4, st.4, tty.4, ttyS.4, vcs.4, veth.4, wavelan.4, acct.5, charmap.5, core.5, dir_colors.5, elf.5, filesystems.5, ftpusers.5, gai.conf.5, group.5, host.conf.5, hosts.5, hosts.equiv.5, intro.5, issue.5, locale.5, motd.5, networks.5, nologin.5, nscd.conf.5, nss.5, nsswitch.conf.5, passwd.5, proc.5, protocols.5, repertoiremap.5, resolv.conf.5, rpc.5, securetty.5, services.5, shells.5, slabinfo.5, sysfs.5, termcap.5, tmpfs.5, ttytype.5, tzfile.5, utmp.5, intro.6, address_families.7, aio.7, armscii-8.7, arp.7, ascii.7, attributes.7, boot.7, bootparam.7, bpf-helpers.7, capabilities.7, cgroup_namespaces.7, cgroups.7, charsets.7, complex.7, cp1251.7, cp1252.7, cpuset.7, credentials.7, ddp.7, environ.7, epoll.7, fanotify.7, feature_test_macros.7, fifo.7, futex.7, glob.7, hier.7, hostname.7, icmp.7, inode.7, inotify.7, intro.7, ip.7, ipc_namespaces.7, ipv6.7, iso_8859-1.7, iso_8859-10.7, iso_8859-11.7, iso_8859-13.7, iso_8859-14.7, iso_8859-15.7, iso_8859-16.7, iso_8859-2.7, iso_8859-3.7, iso_8859-4.7, iso_8859-5.7, iso_8859-6.7, iso_8859-7.7, iso_8859-8.7, iso_8859-9.7, kernel_lockdown.7, keyrings.7, koi8-r.7, koi8-u.7, landlock.7, libc.7, locale.7, mailaddr.7, man-pages.7, man.7, math_error.7, mount_namespaces.7, mq_overview.7, namespaces.7, netdevice.7, netlink.7, network_namespaces.7, nptl.7, numa.7, operator.7, packet.7, path_resolution.7, persistent-keyring.7, pid_namespaces.7, pipe.7, pkeys.7, posixoptions.7, process-keyring.7, pthreads.7, pty.7, queue.7, random.7, raw.7, regex.7, rtld-audit.7, rtnetlink.7, sched.7, sem_overview.7, session-keyring.7, shm_overview.7, sigevent.7, signal-safety.7, signal.7, sock_diag.7, socket.7, spufs.7, standards.7, suffixes.7, symlink.7, system_data_types.7, sysvipc.7, tcp.7, termio.7, thread-keyring.7, time.7, time_namespaces.7, udp.7, udplite.7, unicode.7, units.7, unix.7, uri.7, user-keyring.7, user-session-keyring.7, user_namespaces.7, utf-8.7, uts_namespaces.7, vdso.7, vsock.7, x25.7, xattr.7, iconvconfig.8, intro.8, ld.so.8, ldconfig.8, nscd.8, sln.8, tzselect.8: tstamp Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-08memfd_create.2, mlock.2, poll.2, select.2, fopen.3, capabilities.7: tfixŠtěpán Němec1-2/+2
Signed-off-by: Štěpán Němec <stepnem@smrk.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-08unix.7: fix section reference wrt lengthMike Frysinger1-1/+1
The description of Linux path length handling has always been in the BUGS section. The commit that added this see-also note incorrectly referred to the NOTES section instead. Signed-off-by: Mike Frysinger <vapier@gentoo.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-09-15Various pages: EXAMPLES: Use unsigned types for loop iteratorsAlex Colomar4-10/+10
Looping with unsigned types is safer. See the link below. When the iterators are used for accessing an array, use size_t; otherwise, use the most appropriate unsigned type, which in most cases is just 'unsigned int'. Also adjust other variables that have to interact with the iterators, to avoid comparison of integers of different signedness. Link: <https://gustedt.wordpress.com/2013/07/15/a-praise-of-size_t-and-other-unsigned-types/> Cc: Jens Gustedt <jens.gustedt@inria.fr> Signed-off-by: Alex Colomar <alx.manpages@gmail.com>
2022-09-15ipv6.7: wfixAlex Colomar1-2/+2
Fixes: 77117f4fc55addbb657d1c87e2f86911d7e432c9 Reported-by: Donald Buczek <buczek@molgen.mpg.de> Signed-off-by: Alex Colomar <alx.manpages@gmail.com>
2022-09-13Various pages: EXAMPLES: Use <err.h> functionsAlex Colomar2-18/+11
When reporting errors, prefer using conventional <err.h> functions, rather than home-made macros. Home-made macros are necessary for portable programs, so in documentation about portable functions, keep using the macros. However, in the documentation for functions that are only available in GNU/Linux and/or BSD systems, prefer <err.h>, which is available in both systems. Do the same in example programs documenting portable functions but in which we already require _GNU_SOURCE for some other reason. Signed-off-by: Alex Colomar <alx.manpages@gmail.com>
2022-09-09Revert "src.mk, All pages: Move man* to man/"Alejandro Colomar168-0/+54492
This reverts commit 70ac1c4785fc1e158ab2349a962dba2526bf4fbc. Link: <https://lore.kernel.org/linux-man/YxcV4h+Xn7cd6+q2@pevik/T/> Reported-by: Petr Vorel <pvorel@suse.cz> Reported-by: Jakub Wilk <jwilk@jwilk.net> Cc: Stefan Puiu <stefan.puiu@gmail.com> Signed-off-by: Alex Colomar <alx.manpages@gmail.com>
2022-09-05src.mk, All pages: Move man* to man/Alejandro Colomar168-54492/+0
The root of the repository is becoming a bit overpopulated and unorganized, due to the recent addition of more mandirs, and more informative and configuration files too. Let's create a specific mandir <man/> that contains the mandirs <man[1-8]*>. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-09-01sysvipc.7: tfixŠtěpán Němec1-1/+1
Signed-off-by: Štěpán Němec <stepnem@gmail.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-27man7/regex.7: change "\o'o\(ha'"to a real character "\(^o" (o circumflex)Bjarni Ingi Gislason1-3/+3
Use real accented characters instead of producing them by overstriking the letter with the diacritic mark. Signed-off-by: Bjarni Ingi Gislason <bjarniig@vortex.is> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-25Various pages: Fit rendered pages in 80 columnsAlejandro Colomar3-5/+7
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-25Revert "Many pages: Document fixed-width types with ISO C naming"Alejandro Colomar6-110/+92
This reverts commit 2294974b3a1341e457edb682c08c5f4b2d14675e. Reported-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-24Many pages: Document fixed-width types with ISO C namingman-pages-6.0-rc1Alejandro Colomar6-92/+110
Kernel __u64 and similar types are ABI-compatible, and mostly API-compatible with ISO C types. User-space programmers don't care about kernel details, and should only use libc types. Document syscalls and structures provided by the Linux kernel as if they used libc types. There's work in the kernel to remove this small API incompatibility, which is only for pointers or printf specifiers. Since I couldn't find any structure that uses pointers, there shouldn't be any issues here. Also, the only pointer I found was in a syscall parameter, but since syscall(2) doesn't check its arguments' types, we're also safe there. This patch doesn't go without controversy. Check the discussions in the links below. Found with: $ grep -rn '\b_*[su][8136][624]*\b' man* \ | grep -v -e /bpf-helpers.7 -e /proc.5 -e /epoll_event.3type -e /wcscmp.3 \ -e /crypt.3 -e /mempcpy.3 -e /memcmp.3 -e /string.3 -e /wcsncmp.3 \ -e /wcscasecmp.3 -e /wmemcmp.3 -e /strcasecmp.3 -e /bcmp.3 \ -e /bstring.3 -e /endian.3 -e /strverscmp.3 -e /wcsncasecmp.3 \ -e /strcoll.3 -e /strcmp.3 \ | tee /dev/tty \ | wc -l; Link: <https://lore.kernel.org/linux-man/20210423230609.13519-1-alx.manpages@gmail.com/T/> Link: <https://lore.kernel.org/lkml/YZvIlz7J6vOEY+Xu@yuki/T/> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com> Nacked-by: Alexei Starovoitov <ast@kernel.org> Nacked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Nacked-by: Daniel Borkmann <daniel@iogearbox.net> Acked-by: Zack Weinberg <zackw@panix.com> Cc: LKML <linux-kernel@vger.kernel.org> Cc: glibc <libc-alpha@sourceware.org> Cc: GCC <gcc-patches@gcc.gnu.org> Cc: bpf <bpf@vger.kernel.org> Cc: LTP List <ltp@lists.linux.it> Cc: Linux API <linux-api@vger.kernel.org> Cc: linux-arch <linux-arch@vger.kernel.org> Cc: David Laight <David.Laight@ACULAB.COM> Cc: Joseph Myers <joseph@codesourcery.com> Cc: Florian Weimer <fweimer@redhat.com> Cc: Daniel Borkmann <daniel@iogearbox.net> Cc: Cyril Hrubis <chrubis@suse.cz> Cc: David Howells <dhowells@redhat.com> Cc: Arnd Bergmann <arnd@arndb.de> Cc: Florian Weimer <fweimer@redhat.com> Cc: Rich Felker <dalias@libc.org> Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2022-08-21man-pages.7: Document recent changes to .THAlejandro Colomar1-29/+6
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com> Cc: Jakub Wilk <jwilk@jwilk.net> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Cc: Ingo Schwarze <schwarze@openbsd.de> Cc: Michael Kerrisk <mtk.manpages@gmail.com>
2022-08-21All pages: Remove the 5th argument to .THAlejandro Colomar120-120/+120
Now that we have the LIBRARY section, and a 4th argument that already tells that it's a page from the Linux man-pages project, the 5th argument isn't telling any information that the default value wouldn't. So let's just remove it. Scripted change: $ find man* -type f \ | xargs sed -Ei '/^.TH /s/(.TH +[^ ]+ +[^ ]+ +[^ ]+ +"[^"]+") .*/\1/' Acked-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com> Cc: Ingo Schwarze <schwarze@openbsd.de> Cc: Michael Kerrisk <mtk.manpages@gmail.com>
2022-08-21All pages: Replace the 4th argument to .TH by "Linux man-pages (unreleased)"Alejandro Colomar120-120/+120
On 8/20/22 13:57, Alejandro Colomar wrote: > On 8/20/22 07:43, G. Branden Robinson wrote: >> >> In my opinion it would benefit readers of the Linux man-pages if the >> fourth argument to `TH` were what it is in many other man pages: an >> identifier for the name and version number of the release originating >> them. In every page it would be clear what version of the man-pages was >> being viewed. Little sophistication would be demanded of the user to >> check the Web to determine the relative age of the pages, independently >> of the modification date of the particular page. Such usage would be >> congruent with the argument's purpose in AT&T and BSD Unix, where this >> datum was "7th Edition", "System III", or "4.2 Berkeley Distribution", >> or similar. > > I thought about it in the past... That field was the only thing that > said where a function came from. If we removed GNU (or something else), > how would someone know where does the function or whatever comes from?? > > I guess that's also why the colophon was appended to the pages by > Michael. Since we couldn't use the 4th field for that, we had to have a > COLOPHON section. > > However, the addition of the LIBRARY section seems to fix this issue, > and so now we have an even more precise way to determine where a given > function comes from (including the library file name, and the linker > option). > > This gives me another argument for those who don't like to have a > LIBRARY section for libc stuff (since -lc is unnecessary), and consider > it noise. > >> >> Further, as the libc-related man pages in this project expand coverage >> to other libcs than GNU's, the alternatives to the empty string >> proferred in man-pages(7) seem less and less appropriate. > > Agree. LIBRARY seems much more appropriate for that purpose. > > And this helps remove the COLOPHON section (or at least, we don't need > to autogenerate it, since the version number now comes in .TH, and the > COLOPHON is static; so I can even move it to a smaller REPORTING BUGS > section). Scripted change: $ find man* -type f \ |xargs sed -Ei '/^.TH /s/(.TH +[^ ]+ +[^ ]+ +[^ ]+) +"[^"]*"/\1 "Linux man-pages (unreleased)"/' $ find man* -type f \ |xargs sed -Ei '/^.TH /s/(.TH +[^ ]+ +[^ ]+ +[^ ]+) +[^" ]+/\1 "Linux man-pages (unreleased)"/' $ git restore man5/tzfile.5 $ git restore man8/zdump.8 $ git restore man8/zic.8 $ git restore man7/bpf-helpers.7 Link: <https://lore.kernel.org/linux-man/20220819180323.dbsgxh5qvcjabjm6@jwilk.net/T/#u> Reported-by: Jakub Wilk <jwilk@jwilk.net> Reported-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com> Cc: Ingo Schwarze <schwarze@openbsd.de> Cc: Michael Kerrisk <mtk.manpages@gmail.com>
2022-08-20tcp.7: tfixJakub Wilk1-1/+1
Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-20fanotify.7: tfixJakub Wilk1-1/+1
Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-16spufs.7: tfixAlejandro Colomar1-2/+2
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-15spufs.7: wfix + ffixAlejandro Colomar1-6/+10
Reported-by: Ingo Schwartze <schwarze@openbsd.org> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-15futex.2, futex.7: {ftp://ftp => https://mirrors}.kernel.orgнаб1-1/+1
The former doesn't exist; the latter is the new location with seemingly compatible data Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-15cgroups.7: Document memory_recursiveprot mount optionBrett Holman1-0/+6
Signed-off-by: Brett Holman <bholman.devel@gmail.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-02spufs.7: ffixAlejandro Colomar1-1/+4
Use tbl(1) instead of a magic sequence of spaces and tabs to get a nice formatting. This fixes the following warnings: mandoc: man7/spufs.7:748:7: WARNING: tab in filled text mandoc: man7/spufs.7:748:14: WARNING: tab in filled text mandoc: man7/spufs.7:748:22: WARNING: tab in filled text mandoc: man7/spufs.7:748:32: WARNING: tab in filled text mandoc: man7/spufs.7:748:34: WARNING: tab in filled text Reported-by: 'make lint-man' Reported-by: mandoc(1) Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-02ioctl_userfaultfd.2, fanotify.7: ffixAlejandro Colomar1-1/+1
Reported-by: 'make lint-man' Reported-by: groff(1) Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-02man-pages.7: ffixAlejandro Colomar1-39/+55
Use tables to represent tables. Use .EX/.EE to represent a code example. Use \& to prevent .SS of being interpreted as man(7) source. an.tmac:man7/man-pages.7:900: style: 5 leading space(s) on input line an.tmac:man7/man-pages.7:901: style: 5 leading space(s) on input line an.tmac:man7/man-pages.7:902: style: 5 leading space(s) on input line an.tmac:man7/man-pages.7:903: style: 5 leading space(s) on input line an.tmac:man7/man-pages.7:965: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:966: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:967: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:968: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:969: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:970: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:978: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:979: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:980: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:981: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:982: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:983: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:984: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:985: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:986: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:987: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:988: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:989: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:990: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:991: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:992: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:993: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:994: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:995: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:996: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:997: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:1003: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:1004: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:1005: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:1006: style: 4 leading space(s) on input line an.tmac:man7/man-pages.7:1137: style: 4 leading space(s) on input line Reported-by: 'make lint-man' Reported-by: groff(1) Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-01xattr.7: wfixŠtěpán Němec1-2/+2
(My original intention was to just fix the grammar ("an attribute names is"), but, on second thought, the whole sentence didn't read very well.) Signed-off-by: Štěpán Němec <stepnem@gmail.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-29Many pages: Use STANDARDS instead of CONFORMING TOAlejandro Colomar25-27/+27
STANDARDS seems to be much more extended than CONFORMING TO. For consistency across the whole manual pages corpus, let's try to unify, by following the most commonly used section name. On 7/27/22 12:49, Ingo Schwarze wrote: > Alejandro Colomar wrote on Tue, Jul 26, 2022 at 02:02:56PM +0200: > > We use CONFORMING TO in Linux. Don't know why; just history, I guess. > > See man-pages(7). > > Weird. > > I failed to find a single instance of "CONFORMING TO" in AT&T UNIX > (including v6, PWB, v7, 32v, v8, v10, System III, SVR1, SVR2) nor in > any version of UCB CSRG BSD. So considering that System V and BSD are > widely considered the two main original branches of the development > of Unix-like operating systems and Linux is often considered to have > drawn inspiration from both, the section name "CONFORMING TO" does > not appear to be a UNIX thing. For example, Aeleen Frisch, "Essential > System Administration", O'Reilly, Cambridge 1995, considers Linux > as slightly more influenced by 4.3BSD than by System V Release 3. > > STANDARDS, on the other hand, is present since 4.3BSD-Reno (June 1990). > > 4.3BSD-Reno predates the first version of the Linux kernel by more than > a year, and the first Linux manual pages probably for longer than that. > > So i have no idea where "CONFORMING TO" may have come from. Scripted change: $ find man* -type f | xargs sed -i 's/CONFORMING TO/STANDARDS/' plus a few manual fixes to the following files: - man2/getrlimit.2 - man3/syslog.3 - scripts/bash_aliases Reported-by: Ingo Schwarze <schwarze@openbsd.org> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-26man-pages.7: Document CAVEATS sectionAlejandro Colomar1-0/+5
CAVEATS is an interesting section. There's a slight difference between CAVEATS and BUGS. We usually have a hard time fitting what would go into CAVEATS into other sections (usually BUGS and NOTES); it would be easier if we had the section. Let's add it. This section has been used in manual pages by authors from a wide range of projects including AT&T, Korn shell, Perl, GNU and BSD since the early 1980s. Using the section was first officially recommended in 2002 by the file </usr/share/misc/mdoc.template> in NetBSD and OpenBSD. Reported-by: Ingo Schwarze <schwarze@usta.de> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-22man-pages.7: The linker flag is not always necessaryAlejandro Colomar1-2/+2
See for example pages for types Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-22man-pages.7: Document LIBRARY sectionAlejandro Colomar1-0/+9
Reported-by: "Theodore Ts'o" <tytso@mit.edu> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-22regex_t.3type, regmatch_t.3type, regoff_t.3type, system_data_types.7: Move ↵Alejandro Colomar1-79/+0
regex_t, regmatch_t, and regoff_t to a separate page Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-22stat.3type, system_data_types.7: Move stat to a separate pageAlejandro Colomar1-140/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-22timer_t.3type, system_data_types.7: Move timer_t to a separate pageAlejandro Colomar1-22/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-21timespec.3type, system_data_types.7: Move timespec to a separate pageAlejandro Colomar1-64/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-21timeval.3type, system_data_types.7: Move timeval to a separate pageAlejandro Colomar1-31/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-21va_list.3, system_data_types.7: Move va_list to a separate pageAlejandro Colomar1-30/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-21bpf-helpers.7: Refresh pageAlejandro Colomar1-44/+1146
The script for generating this page is hosted in the Linux kernel repository, as <scripts/bpf_doc.py>. Run it as: $ /path/to/linux//scripts/bpf_doc.py | rst2man > man7/bpf-helpers.7 Link: <https://lore.kernel.org/linux-man/CA+FoirA-FeYeA5ZPgCvo55Hg_dfe7dT54Co8CkU9wW8yemFcJA@mail.gmail.com/T/> Cc: Daniel Borkmann <daniel@iogearbox.net> Cc: Quentin Monnet <quentin.monnet@netronome.com> Cc: Rumen Telbizov <rumen.telbizov@menlosecurity.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-21void.3, void.3type, system_data_types.7: Move void* to a separate pageAlejandro Colomar1-73/+0
Also fix the page to be in man3type, not in man3. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-21suseconds_t.3type, time_t.3type, useconds_t.3type, system_data_types.7: Move ↵Alejandro Colomar1-95/+0
time_t, suseconds_t, and useconds_t to a separate page Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-20ptrdiff_t.3type, system_data_types.7: Move ptrdiff_t to a separate pageAlejandro Colomar1-39/+2
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-20size_t.3type, system_data_types.7: Move size_t to a separate pageAlejandro Colomar1-102/+1
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-20loff_t.3type, off64_t.3type, off_t.3type, system_data_types.7: Move off_t ↵Alejandro Colomar1-86/+1
and off64_t to separate page, and document loff_t Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-04fanotify.7, fanotify_init.2, fanotify_mark.2: Document FAN_RENAMEAmir Goldstein1-1/+5
FAN_RENAME is a new event type that includes information about both old and new directory entries. It is a successor of the two separate FAN_MOVED_TO/FROM events, but those event types are still supported. Reviewed-by: Matthew Bobrowski <repnop@google.com> Reviewed-by: Jan Kara <jack@suse.cz> Signed-off-by: Amir Goldstein <amir73il@gmail.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-04fanotify.7, fanotify_init.2: Document FAN_REPORT_TARGET_FIDAmir Goldstein1-14/+13
FAN_REPORT_TARGET_FID adds an information record about the child to directory entry modification events (create/delete/move). This flag also adds sanity checks that directory modification events (create,delete,moved) cannot be set in mask of a non-dir inode mark. Note that while FAN_REPORT_TARGET_FID was merged to v5.17, the sanity checks resulting in ENOTDIR were merged as fix commits ceaf69f8eadc ("fanotify: do not allow setting dirent events in mask of non-dir") and 8698e3bab4dd ("fanotify: refine the validation checks on non-dir inode mask") in later kernel releases. Reviewed-by: Matthew Bobrowski <repnop@google.com> Reviewed-by: Jan Kara <jack@suse.cz> Signed-off-by: Amir Goldstein <amir73il@gmail.com> [alx: ffix] Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-03environ.7: align PWD with the standardнаб1-2/+6
Issue 7, 8.3: PWD This variable shall represent an absolute pathname of the current working directory. It shall not contain any components that are dot or dot-dot. The value is set by the cd utility, and by the sh utility during initialization. Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-19standards.7: tfixAlejandro Colomar1-1/+1
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-17ssize_t.3type, system_data_types.7: Move ssize_t to a separate pageAlejandro Colomar1-90/+11
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-17fanotify.7, fanotify_mark.2: Document FAN_FS_ERRORGabriel Krisman Bertazi1-0/+71
FAN_FS_ERROR is a new event for fanotify to report filesystem errors that might lead to some corruption. This documents how to use the feature and specific caveats. Reviewed-by: Jan Kara <jack@suse.cz> Reviewed-by: Amir Goldstein <amir73il@gmail.com> Reviewed-by: Matthew Bobrowski <repnop@google.com> Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-16ctime.3, strptime.3, time.7: Refer to tm(3type)Alejandro Colomar1-1/+1
Instead of repeating the documentation of tm(3type) in pages that use it, just refer to it. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-05-24fanotify: Document FAN_REPORT_PIDFD FeatureMatthew Bobrowski1-38/+183
Update the fanotify API documentation to include details on the new FAN_REPORT_PIDFD feature. This patch also includes a generic section describing the concept of information records which are supported by the fanotify API. Signed-off-by: Matthew Bobrowski <repnop@google.com> Reviewed-by: Jan Kara <jack@suse.cz> Reviewed-by: Amir Goldstein <amir73il@gmail.com> [alx: wsfix, ffix] Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-04-02uri.7: Be more precise in RFC referenceAlejandro Colomar1-1/+2
RFC 7595 points to RFC 3986. Let's refer to where the info actually is. Reported-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-03-29Revert "uri.7: The term URL is deprecated, in favor of URI"Alejandro Colomar1-52/+49
This reverts commit 97bf2b7a7287b8e1672967f2df31f4a80a43edae. That commit was incorrect, as Jakub pointed out. Link: linux-man@ <https://lore.kernel.org/linux-man/36b89bec-1def-e87c-5477-c87f2f0e48e9@gmail.com/T/> Reported-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-03-28uri.7: Update RFC reference (2718 -> 7595)Alejandro Colomar1-1/+1
There's no significant change that affects this paragraph, so simply update the reference to the obsolete RFC, to refer to the current one. Cc: NGINX Unit <unit@nginx.org> Cc: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-03-28uri.7: The term URL is deprecated, in favor of URIAlejandro Colomar1-49/+52
See RFCs 4395 (obsoleted by 7595) and 7595. So, since URI and URL have been used as synonims and it wasn't clear to most people what the difference was, the RFCs seem to have explicitly avoided URL, and now use URI as the only term, which still means what it meant (so now URL is just a synonim for URI). This commit replaces (almost all) occurences of URL by URI, except when it is referring to the old term itself. Keep some legacy info just for readers to understand this. Cc: NGINX Unit <unit@nginx.org> Cc: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-03-28uri.7: Update RFC reference (2279 -> 3629)Alejandro Colomar1-1/+1
There's no significant change that affects the manual page, so simply update the reference to refer to the new one. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-03-20glob.7: ffixAlejandro Colomar1-1/+1
Fix error accidentally introduced in 7b97eb9ff04e Suggested-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-03-20Many pages: Fix style issues reported by `make lint-mandoc`Alejandro Colomar12-41/+53
Plus some other found in the process. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-03-20Many pages: Fix style issues reported by `make lint-groff`Alejandro Colomar65-748/+872
Plus some other found in the process. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-27man-pages.7: Document LIBRARY section for man2 and man3Alejandro Colomar1-0/+1
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-25Various pages: [Linux-man-pages-copyleft] Use SPDX-License-IdentifierAlejandro Colomar50-1070/+50
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-25Various pages: [GPL-2.0-only] Use SPDX-License-IdentifierAlejandro Colomar1-19/+1
$ find man? -type f \ | xargs sed -i '/%%%LICENSE_START(GPLv2/,/%%%LICENSE_END/c\.\\" SPDX-License-Identifier: GPL-2.0-only' Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-25Various pages: [GPL-2.0-or-later] Use SPDX-License-IdentifierAlejandro Colomar44-744/+44
$ find man? -type f \ | xargs sed -i '/%%%LICENSE_START(GPLv2+/,/%%%LICENSE_END/c\.\\" SPDX-License-Identifier: GPL-2.0-or-later' Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-25Various pages: [GPL-1.0-or-later] Use SPDX-License-IdentifierAlejandro Colomar3-9/+3
$ find man? -type f \ | xargs sed -i '/%%%LICENSE_START(GPL_NOVERSION_ONELINE/,/%%%LICENSE_END/c\.\\" SPDX-License-Identifier: GPL-1.0-or-later' Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-25Various pages: [BSD-4-Clause-UC] Use SPDX-License-IdentifierAlejandro Colomar1-29/+1
$ find man? -type f \ | xargs sed -i '/%%%LICENSE_START(BSD_4_CLAUSE_UCB/,/%%%LICENSE_END/c\.\\" SPDX-License-Identifier: BSD-4-Clause-UC' Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-25Various pages: [BSD-3-Clause] Use SPDX-License-IdentifierAlejandro Colomar3-75/+3
$ find man? -type f \ | xargs sed -i '/%%%LICENSE_START(BSD_3_CLAUSE_UCB/,/%%%LICENSE_END/c\.\\" SPDX-License-Identifier: BSD-3-Clause' Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-25futex.7: [MIT] Use SPDX-License-IdentifierAlejandro Colomar1-3/+1
$ find man? -type f \ | xargs sed -i '/%%%LICENSE_START(MIT/,/%%%LICENSE_END/c\.\\" SPDX-License-Identifier: MIT' Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-25intptr_t.3, system_data_types.7: Move uintptr_t to intptr_t.3Alejandro Colomar1-67/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-25intptr_t.3, system_data_types.7: Move text to a separate pageAlejandro Colomar1-64/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-25sockaddr-struct.3, socklen_t.3, system_data_types.7: Move socklen_t to ↵Alejandro Colomar1-27/+0
sockaddr-struct.3 Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24sockaddr-struct.3, system_data_types.3: Move sockaddr to sockaddr-struct.3Alejandro Colomar1-24/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24mode_t.3, system_data_types.7: Move text to a separate pageAlejandro Colomar1-32/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24div_t.3, lldiv_t.3, system_data_types.7: Move lldiv_t to div_t.3Alejandro Colomar1-23/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24div_t.3, ldiv_t.3, system_data_types.7: Move ldiv_t to div_t.3Alejandro Colomar1-23/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24lconv-struct.3, system_data_types.7: Move text to a separate pageAlejandro Colomar1-48/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24intN_t.3, uint16_t.3, uint32_t.3, uint64_t.3, uint8_t.3, uintN_t.3, ↵Alejandro Colomar1-84/+0
system_data_types.7: Move uintN_t to intN_t.3 Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24intN_t.3, system_data_types.7: Move text to a separate pageAlejandro Colomar1-81/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24intmax_t.3, uintmax_t.3, system_data_types.7: Move uintmax_t to intmax_t.3Alejandro Colomar1-55/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24intmax_t.3, system_data_types.7: Move text to a separate pageAlejandro Colomar1-56/+0
I also reworded the text slightly to talk about 'basic integer types', not 'integer types', to more clearly exclude 'extended integer types'. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24div_t.3, imaxdiv_t.3, system_data_types.7: Move imaxdiv_t to div_t.3Alejandro Colomar1-23/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24id_t.3, uid_t.3, system_data_types.7: Move uid_t to id_t.3Alejandro Colomar1-29/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24id_t.3, pid_t.3, system_data_types.7: Move pid_t to id_t.3Alejandro Colomar1-45/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24gid_t.3, id_t.3, system_data_types.7: Move gid_t to id_t.3Alejandro Colomar1-31/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24id_t.3, system_data_types.7: Move text to a separate pageAlejandro Colomar1-23/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24FILE.3, system_data_types.7: Move text to a separate pageAlejandro Colomar1-23/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24fenv_t.3, system_data_types.7: Move fexcept_t to fenv_t.3Alejandro Colomar1-16/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24fenv_t.3, system_data_types.7: Move text to a separate pageAlejandro Colomar1-16/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24select.2, system_data_types.7: Move fd_set to select.2Alejandro Colomar1-21/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24double_t.3, float_t.3, system_data_types.7: Move float_t to double_t.3Alejandro Colomar1-42/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24double_t.3, system_data_types.7: Move text to a separate pageAlejandro Colomar1-42/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24div_t.3, system_data_types.7: Move text to a separate pageAlejandro Colomar1-23/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24dev_t.3, system_data_types.7: Move text to a separate pageAlejandro Colomar1-25/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24clockid_t.3, system_data_types.7: Move text to a separate pageAlejandro Colomar1-22/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24clock_t.3, system_data_types.7: Move text to a separate pageAlejandro Colomar1-24/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24cc_t.3, system_data_types.7: Move text to a separate pageAlejandro Colomar1-16/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24blksize_t.3, system_data_types.7: Move text to a separate pageAlejandro Colomar1-20/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24blkcnt_t.3, system_data_types.7: Move text to a separate pageAlejandro Colomar1-20/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24aiocb-struct.3, system_data_types.7: Move text to a separate pageAlejandro Colomar1-34/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24system_data_types.7: Document useconds_tAlejandro Colomar1-0/+29
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24system_data_types.7: ssize_t: Note that some headers only provide the type ↵Alejandro Colomar1-0/+9
since POSIX.1-2008 Signed-off-by: Alejandro Colomar <alejandro.colomar@exfo.com>
2022-02-24system_data_types.7: Link to the stat structure definitionAlejandro Colomar1-5/+17
The definition of 'struct stat' is not in stat(2) anymore. It is in the same system_data_types(7) page, so link to it. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-02-24stat.2, system_data_types.7: Document 'struct stat' in system_data_types(7)Alejandro Colomar1-0/+141
Move the definition of the struct present in stat(2), and put there a reference to stat-struct(3) instead. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com> Cc: G. Branden Robinson <g.branden.robinson@gmail.com>
2022-02-12packet.7: add description of zero protocol for socketGrzegorz Szpetkowski1-0/+8
According to packet(7), whenever raw packet is created by socket(), it's immediately running, meaning that internal packet_rcv() handler will be triggered and socket buffer will begin allocation of sk_buff until sk_rcvbuf limit is reached. However, by examination of kernel's internal handler packet_create() it looks that kernel handles case of zero protocol in a special manner. When packet_create() is called with arg protocol = 0, __register_prot_hook is not executed, meaning running state is still 0 and most notably, packet handler is not added to kernel list (vide dev_add_pack). I found this behavior invaluable for solving a subtle issue. When process creates raw packet socket to listen for (let's say) all protocols, but limited to a single network interface, then while this interface can set by bind, it may to be too late due to preemption (e.g. if real-time scheduling is used) and/or high-rate of packets on other interfaces, meaning that undesired packets (any count) may be pulled into the socket buffer. The idea is that protocol zero means no packets on receive and an optional call to bind with nonzero sll_procol will act "as if" the originating socket API was called with this (nonzero) protocol. The call to bind(2) is optional. As an example, if user intends to treat the socket as Tx-only, then bind(2) may be skipped. Reported-by: Grzegorz Szpetkowski <gszpetkowski@gmail.com> Link: linux-man@ <https://lore.kernel.org/linux-man/CAMW=dumhWDu6LdhaQCJMskA4yNRBtOHs4iyrG6TP7xRv28AVWA@mail.gmail.com/> Cowritten-by: Alejandro Colomar <alx.manpages@gmail.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com> Signed-off-by Grzegorz Szpetkowski <gszpetkowski@gmail.com>:
2022-02-07capabilities.7: improve internal referencesKir Kolyshkin1-22/+40
Trying to make this man page easier to navigate. Fix a few cases of "see above/below" without a specific reference to a subsection by quoting the subsection name (making it easier to look it up). Use the same formatting rule as used by some of the other existing references, i.e. italicise it. For uniformity, remove words such as "the subsection" and "under", using "(see|described in) <subsection title> (above|below)" template. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-01-30time.7: tfixнаб1-1/+1
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-01-30time.7: tfixнаб1-1/+1
"HZ" is the constant, and has nothing to do with the 50 Hz PAL/60 Hz NTSC mains frequencies Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-01-30units.7: SEE ALSO: Add link to 'The International System of Units'Alejandro Colomar1-0/+4
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com> Cc: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
2022-01-26man-pages.7: wfixAlejandro Colomar1-1/+1
'clauses' is clearer than 'sentence clauses' in this case; there's no ambiguity. Reported-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-01-11pkeys.7: wfixнаб1-2/+3
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-01-08pkeys.7: Rely on the glibc implementationsStephen Kitt1-38/+0
glibc 2.27 added implementations of pkey_set(), pkey_mprotect(), pkey_alloc(), and pkey_free(); rely on those instead of defining them in the example. wrpkru() is only used in pkey_set() and can be removed too (it's the internal-use-only pkey_write() in glibc). Signed-off-by: Stephen Kitt <steve@sk2.org> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-01-08pkeys.7: Update the example to match glibcStephen Kitt1-9/+10
glibc 2.27 introduced support for the pkeys functions, but the glibc versions don't match those declared in the example. Update the example to match glibc, and avoid declaring the functions if glibc is new enough. Signed-off-by: Stephen Kitt <steve@sk2.org> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-01-03system_data_types.7: note struct timespec::tv_nsec type for x32 and portabilityнаб1-0/+31
There are three files that govern userspace struct timespec on glibc: 1. bits/wordsize.h, defining: (a) __WORDSIZE to 32 on ILP32 and 64 on LP64 (b) on x32: __SYSCALL_WORDSIZE to 64 2. bits/timesize.h, defining (a) __TIMESIZE to __WORDSIZE, except on x32 where it's 64 3. bits/types/struct_timespec.h, declaring struct timespec as: struct timespec { __time_t tv_sec; /* Seconds. */ #if __WORDSIZE == 64 \ || (defined __SYSCALL_WORDSIZE && __SYSCALL_WORDSIZE == 64) \ || __TIMESIZE == 32 __syscall_slong_t tv_nsec; /* Nanoseconds. */ #else # if __BYTE_ORDER == __BIG_ENDIAN int: 32; /* Padding. */ long int tv_nsec; /* Nanoseconds. */ # else long int tv_nsec; /* Nanoseconds. */ int: 32; /* Padding. */ # endif #endif }; this has two side-effects: struct timespec (a) is always sizeof==time_t+8, and (b) has tv_nsec as __syscall_slong_t *and* !is_same<__syscall_slong_t, long> if using LP64 syscalls on an ILP32 system, i.e. on x32. This means, that the simplified struct timespec { time_t tv_sec; /* Seconds */ long tv_nsec; /* Nanoseconds [0 .. 999999999] */ }; declaration is *invalid* for x32, where struct timespec::tv_nsec is an int64_t (long long). Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2021-12-18mount_setattr.2, proc.5, netlink.7, tcp.7: tfixSamanta Navarro2-2/+2
Typos found with codespell. Signed-off-by: Samanta Navarro <ferivoz@riseup.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2021-12-18pthread_cancel.3, pthread_cleanup_push_defer_np.3, pthread_setcancelstate.3, ↵Samanta Navarro5-41/+41
pthread_testcancel.3, pthreads.7: tfix Changed cancellation to cancelation. Signed-off-by: Samanta Navarro <ferivoz@riseup.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2021-12-06system_data_types.7: timespec: Add tv_nsec range to commentнаб1-1/+1
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2021-11-22fanotify_init.2, fanotify_mark.2, fanotify.7: Configurable limitsAmir Goldstein1-2/+33
Update documentation about the new configurable fanotify limits that will be available from Linux kernel 5.13. Signed-off-by: Amir Goldstein <amir73il@gmail.com> Reviewed-by: Jan Kara <jack@suse.cz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2021-11-13man-pages.7: Add phrasal semantic newlines adviseAlejandro Colomar1-3/+5
Brian W. Kernighan, 1974 [UNIX For Beginners]: [ Hints for Preparing Documents Most documents go through several versions (always more than you expected) before they are finally finished. Accordingly, you should do whatever possible to make the job of changing them easy. First, when you do the purely mechanical operations of typing, type so subsequent editing will be easy. Start each sentence on a new line. Make lines short, and break lines at natural places, such as after commas and semicolons, rather than randomly. Since most people change documents by rewriting phrases and adding, deleting and rearranging sentences, these precautions simplify any editing you have to do later. ] He mentioned phrases, and they are indeed commonly the operands of patches (see this patch's changes (the second part) as an example), so they make for a much better breaking point than random within a clause that is too long to fit a line. The downside is that they are more difficult to automatically spot than clause breaks (which tend to have associated punctuation). But we are humans writing patches, not machines, and therefore we should be able to decide and detect them better. Link: <https://rhodesmill.org/brandon/2012/one-sentence-per-line/> Cc: G. Branden Robinson <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2021-11-13man-pages.7: Update nonbreaking space adviceG. Branden Robinson1-1/+1
* Advise usage of \~ escape instead of \SPACE; the former, a groff extension from circa 1990, has been supported by Heirloom Doctools troff since 2005 and by mandoc since 2019. The advantage is that \~ is an _adjustable_ non-breaking space, so it will typeset non-jarringly both in .EX/.EE examples when filling is off, and in normal running text (which is filled). See linux-man@ list discussion at <https://lore.kernel.org/linux-man/\ 20210729115508.pt6btsqd7g5tuhg6@localhost.localdomain/> and follow-ups. Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2021-11-12tcp.7: Minor tweaks to Wei's patchAlejandro Colomar1-24/+27
- wsfix - Boldface literals (see groff_man(7)). - Replace '\ ' by \~, per Branden's advise. - Use phrasal semantic newlines. - Put '...' in a C comment, to avoid interfering with groff. It has the side effect that the code example is pure C now. - Remove incorrect trailing '.IP'. Cc: Wei Wang <weiwan@google.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2021-11-12tcp.7: Add description for TCP_FASTOPEN and TCP_FASTOPEN_CONNECT optionsWei Wang1-0/+125
TCP_FASTOPEN socket option was added by: commit 8336886f786fdacbc19b719c1f7ea91eb70706d4 TCP_FASTOPEN_CONNECT socket option was added by the following patch series: commit 065263f40f0972d5f1cd294bb0242bd5aa5f06b2 commit 25776aa943401662617437841b3d3ea4693ee98a commit 19f6d3f3c8422d65b5e3d2162e30ef07c6e21ea2 commit 3979ad7e82dfe3fb94a51c3915e64ec64afa45c3 Add detailed description for these 2 options. Also add descriptions for /proc entry tcp_fastopen and tcp_fastopen_key. Signed-off-by: Wei Wang <weiwan@google.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2021-11-11man7: unify socket examplesJeremy Kerr3-3/+3
The udp, tcp and x25 man pages' synopses list the socket() example as all bold, but the socket varname should be italicised. This change unifies these with the example in socket.7 Signed-off-by: Jeremy Kerr <jk@codeconstruct.com.au> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2021-11-03landlock_add_rule.2, landlock_create_ruleset.2, landlock_restrict_self.2, ↵Alejandro Colomar1-25/+26
landlock.7: Minor tweaks to Mickaël's patches - exit(EXIT_FAILURE) instead of return 1, for consistency with the rest of the manual pages. - Use old declarations: variables defined at the top, separate from code. Initialization other than zero doesn't belong there. - Don't break URIs in weird ways (a trailing slash on a new line would be weird). - Break URIs after the slash; not before. Per Branden's advise. - Use uint32_t instead of __u32 in prototypes. - tfix - A few semantic newline improvements. - ffix Cc: Mickaël Salaün <mic@digikod.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2021-11-03landlock.7: Add a new page to introduce LandlockMickaël Salaün1-0/+361
From the user point of view, Landlock is a set of system calls enabling to build and enforce a set of access-control rules. A ruleset can be created with landlock_create_ruleset(2), populated with landlock_add_rule(2) and enforced with landlock_restrict_self(2). This man page gives an overview of the whole mechanism. Details of these system calls are documented in their respective man pages. This is an adaptation of https://www.kernel.org/doc/html/v5.13/userspace-api/landlock.html Signed-off-by: Mickaël Salaün <mic@linux.microsoft.com> Link: https://lore.kernel.org/r/20210818155931.484070-2-mic@digikod.net Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2021-10-02unix.7: Add a description for ENFILE.Kuniyuki Iwashima1-0/+3
When creating UNIX domain sockets, the kernel used to return -ENOMEM on error where it should return -ENFILE. The behaviour has been wrong since 2.2.4 and fixed in the recent commit f4bd73b5a950 ("af_unix: Return errno instead of NULL in unix_create1()."). Signed-off-by: Kuniyuki Iwashima <kuniyu@amazon.co.jp> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2021-09-20packet.7: Minor tweaks to Ralf's patchAlejandro Colomar1-7/+8
Cc: Ralf Baechle <ralf@linux-mips.org> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2021-09-20packet.7: Describe SOCK_PACKET netif name length issues and workarounds.Ralf Baechle1-3/+36
Describe the issues with SOCK_PACKET possibly truncating network interface names in results, solutions and possible workarounds. While the issue is known for a long time it appears to have never been properly documented is has started to bite software antiques including the AX.25 userland badly since the introduction of Predictable Network Interface Names. So let's document it. Signed-off-by: Ralf Baechle <ralf@linux-mips.org> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2021-08-31mount_namespaces.7: Update references to ↵Michael Kerrisk1-4/+4
Documentation/filesystems/sharedsubtree.rst Documentation/filesystems/sharedsubtree.txt has changed to Documentation/filesystems/sharedsubtree.rst. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-31operator.7: Reorder symbols as in the standard (C11)Alejandro Colomar1-4/+4
This makes it easier to compare this page to the standard, to get more details about the rules between operators. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-31operator.7: Fix precedence of the 'cast operator'Alejandro Colomar1-1/+2
Unary operators are mentioned in C11::6.5.3, and casts are in C11::6.5.4 (they are mentioned in order of precedence). And from note 85 (in section 6.5) in that same C11 standard, major subsections 6.5.X are sorted by precedence. As an example (from Jakub), `sizeof(int)+1` is interpreted as `(sizeof(int))+1`, and not `sizeof((int)+1)`. I used C11 and not C18 (the latest) because at least in the draft copy of C18 that I have, there are a few important typos in that section, while the draft copy of C11 that I have is free of those typos. And C11 and C18 are almost identical, with no major changes to the language. Reported-by: David Sletten <david.paul.sletten@gmail.com> Cc: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-27iconv.1, ldd.1, accept.2, access.2, add_key.2, arch_prctl.2, bpf.2, chmod.2, ↵Michael Kerrisk10-10/+10
chown.2, close_range.2, copy_file_range.2, execve.2, execveat.2, fanotify_mark.2, futex.2, futimesat.2, getpriority.2, intro.2, ioctl_tty.2, keyctl.2, link.2, membarrier.2, mkdir.2, mknod.2, mlock.2, mount.2, mount_setattr.2, open.2, open_by_handle_at.2, perf_event_open.2, pidfd_open.2, readlink.2, readv.2, rename.2, request_key.2, seccomp.2, sigaction.2, stat.2, statx.2, symlink.2, syscalls.2, umount.2, unlink.2, utimensat.2, wait.2, bsearch.3, fflush.3, getaddrinfo.3, getauxval.3, getopt.3, getsubopt.3, mkfifo.3, pthread_mutex_consistent.3, pthread_setname_np.3, pthread_tryjoin_np.3, scandir.3, sem_wait.3, stailq.3, strlen.3, strstr.3, termios.3, tsearch.3, wcslen.3, wcstok.3, wordexp.3, proc.5, capabilities.7, cgroups.7, fanotify.7, mount_namespaces.7, namespaces.7, path_resolution.7, pipe.7, posixoptions.7, user_namespaces.7, vdso.7, iconvconfig.8, ld.so.8: tstamp Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-22mount_namespaces.7: tfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-22mount_namespaces.7: Minor wording fixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-21mount_namespaces.7: wfix: use numbered cross-references in list of ↵Michael Kerrisk1-8/+8
restrictions in NOTES Done to make the list easier to navigate. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-20mount_namespaces.7: Rewrite locked mounts examples to use/etc/shadowMichael Kerrisk1-17/+23
See https://lore.kernel.org/linux-man/20210817140649.7pmz5qcelgjzgxtz@wittgenstein/ Subject: Re: [PATCHi, man-pages] mount_namespaces.7: More clearly explain "locked mounts" Date: Tue, 17 Aug 2021 16:06:49 +0200 Message-ID: <20210817140649.7pmz5qcelgjzgxtz@wittgenstein> Reported-by: Christian Brauner <christian.brauner@ubuntu.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-20mount_namespaces.7: Note that it is possible to stack a mount on top of a ↵Michael Kerrisk1-0/+14
locked mount Reported-by: Eric W. Biederman <ebiederm@xmission.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-20mount_namespaces.7: wfixMichael Kerrisk1-3/+3
Reported-by: Eric W. Biederman <ebiederm@xmission.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-20mount_namespaces.7: Minor wording clean-ups in discussion of less privileged ↵Michael Kerrisk1-12/+12
namespaces Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-20mount_namespaces.7: wfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-20mount_namespaces.7: Terminology clean-up: "mount point" ==> "mount"Michael Kerrisk1-83/+83
Many times, this page use the terminology "mount point", where "mount" would be better. A "mount point" is the location at which a mount is attached. A "mount" is an association between a filesystem and a mount point. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-20mount_namespaces.7: wfixMichael Kerrisk1-1/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-20mount_namespaces.7: wfixMichael Kerrisk1-8/+7
The correct terminology is "less privileged mount namespace" (not "less privileged user namespace"). Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-20mount_namespaces.7: Relocate the "Restrictions on mount namespaces" subsectionMichael Kerrisk1-266/+265
The "Restrictions on mount namespaces" subsection belongs lower in the page, following the discussion of concepts (e.g., shared subtrees and propagation) that are discussed elsewhere in the page. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-20mount_namespaces.7: Repair earlier text after injection of new list item in ↵Michael Kerrisk1-1/+4
previous commit The previous commit injected a large block of text into a list, separating one example in the previous list item from a "continuation" in the following list item. repair that. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-20mount_namespaces.7: Add further details on locked mounts in a ↵Michael Kerrisk1-0/+113
less-privileged user namespace Reported-by: Eric W. Biederman <ebiederm@xmission.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-20mount_namespaces.7: More clearly explain the notion of locked mountsMichael Kerrisk1-1/+74
For a long time, this manual page has had a brief discussion of "locked" mounts, without clearly saying what this concept is, or why it exists. Expand the discussion with an explanation of what locked mounts are, why mounts are locked, and some examples of the effect of locking. Thanks to Christian Brauner for a lot of help in understanding these details. Reported-by: Christian Brauner <christian.brauner@ubuntu.com> Acked-by: Christian Brauner <christian.brauner@ubuntu.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-19user_namespaces.7: Add a definition of "global root"Michael Kerrisk1-0/+6
Reported-by: Eric W. Biederman <ebiederm@xmission.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-18user_namespaces.7: tfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-18user_namespaces.7: Document /proc/PID/projid_mapMichael Kerrisk1-0/+42
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-18user_namespaces.7: Minor wording improvementMichael Kerrisk1-2/+2
Mainly in preparation for the following patch on project IDs maps. Add some words that will make the parallels between the rules for updating uid_map and projid_map clearer. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-18fanotify_mark.2, link.2, mount.2, umount.2, proc.5, cgroups.7, fanotify.7: ↵Michael Kerrisk2-9/+9
Terminology clean-up: "mount point" ==> "mount" Many times, these pages use the terminology "mount point", where "mount" would be better. A "mount point" is the location at which a mount is attached. A "mount" is an association between a filesystem and a mount point. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-13mount_namespaces.7: SEE ALSO: add mount_setattr(2)Michael Kerrisk1-0/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-12mount_namespaces.7: tfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-11capabilities.7: Add a reference to user_namespaces(7) for CAP_SETFCAPMichael Kerrisk1-4/+3
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-11user_namespaces.7: Improve description of the CAP_SETFCAP requirement when ↵Michael Kerrisk1-3/+39
mapping UID 0 Kir Kolyshkin made a start, but I think much more needs to be said... Reviewed-by: Serge E. Hallyn <serge@hallyn.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-10man-pages.7: wfix: s/null character/null byte/Michael Kerrisk1-1/+1
Reported-by: Stefan Kanthak <stefan.kanthak@nexgo.de> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-10unicode.7: tfixMichael Kerrisk1-1/+1
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-09path_resolution.7: tfix + srcfixAlejandro Colomar1-2/+2
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-09path_resolution.7: Improve description of trailin slashesMichael Kerrisk1-3/+4
See https://bugzilla.kernel.org/show_bug.cgi?id=212385 some/path/dir/ is not always the same as some/path/dir/: $ mkdir u $ rmdir u/. rmdir: failed to remove 'u/.': Invalid argument $ rmdir u $ The text in POSIX.1-2018 Section 4.13 ("Pathname Resolution") is helpful in pointing to a better wording. Reported-by: Askar Safin <safinaskar@mail.ru> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-09localedef.1, access.2, ioctl_console.2, ioctl_fslabel.2, openat2.2, write.2, ↵Michael Kerrisk4-6/+10
dlsym.3, getopt.3, nl_langinfo.3, termios.3, xcrypt.3, hosts.equiv.5, nsswitch.conf.5, cgroups.7, man-pages.7, netlink.7, system_data_types.7: srcfix: semantic newlines Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
generated by cgit 1.2.3-korg (git 2.43.0) at 2025-11-28 18:32:10 +0000