aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2022-08-30ioctl_ns.2, stat.2: Drop unneeded uintmax_t castsJakub Wilk2-9/+9
major() and minor() return unsigned int, so the typecasts to uintmax_t are not needed. Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-30termios.3: mention the integer types in SEE ALSOнаб1-0/+3
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-30cc_t.3type, speed_t.3type, tcflag_t.3type: document all togetherнаб3-3/+13
speed_t and tcflag_t were both unmentioned in general Issue 7 has this to say: The <termios.h> header shall define the following data types through typedef: cc_t Used for terminal special characters. speed_t Used for terminal baud rates. tcflag_t Used for terminal modes. The above types shall be all unsigned integer types. Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-28lint-man.mk: Redirect groff output to stderrAlejandro Colomar1-1/+1
groff(1) is being used to warn. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-28cmd.mk, lint-man.mk: Use MANWIDTH instead of a hardcoded 80Alejandro Colomar2-3/+7
Also need another variable set to MANWIDTH - 2, since troff needs room for two extra characters for some reason. Cc: Ralph Corderoy <ralph@inputplus.co.uk> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-28lint-man.mk: Use ascii instead of utf8Alejandro Colomar1-1/+1
This is relevant for tables, which will now use ASCIIart, instead of pretty multi-byte characters which interfere with the calculation of the line width. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-28lint-man.mk: Use grep through its command variableAlejandro Colomar1-1/+1
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-28lint-man.mk: Remove highlighting in a more robust wayAlejandro Colomar1-3/+12
'grotty -c | col -bx' is more reliable, and far more readable. Suggested-by: Ralph Corderoy <ralph@inputplus.co.uk> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-28lint-man.mk: Specify the output device through a variableAlejandro Colomar1-2/+4
Suggested-by: Ralph Corderoy <ralph@inputplus.co.uk> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-28lint-man.mk: Use a pipeline instead of the groff(1) wrapperAlejandro Colomar1-13/+25
This more explicitly shows how stuff really works, and allows inspecting some intermediate steps in case it may be necessary. Cc: Ralph Corderoy <ralph@inputplus.co.uk> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Cc: <groff@gnu.org> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-27lint-man.mk: Use UTF-8 outputAlejandro Colomar1-1/+1
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-26lint-man.mk: Force groff(1) to use 80 columnsAlejandro Colomar1-0/+1
Cc: Ralph Corderoy <ralph@inputplus.co.uk> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-26pthread_setname_np.3: Rename 'len' to 'size'Alejandro Colomar1-3/+3
The parameter doesn't represent a string length (strlen(3)), but a buffer size (sizeof()). Use a more proper name. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-25confstr.3: Rename 'len' to 'size'Alejandro Colomar1-6/+6
The parameter doesn't represent a string length (strlen(3)), but a buffer size (sizeof()). Use a more proper name. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-25Various pages: Fit rendered pages in 80 columnsAlejandro Colomar6-12/+15
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-25wcswidth.3, wcwidth.3, veth.4: Fix accidents in .THAlejandro Colomar3-3/+3
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-25lint-man.mk: Check that rendered pages don't go past 80 columnAlejandro Colomar1-1/+4
Until groff(1) or mandoc(1) add such a warning, this is good enough. Link: <https://lists.gnu.org/archive/html/groff/2022-08/msg00197.html> Link: <https://stackoverflow.com/a/24005600/6872717> Cc: Ingo Schwarze <schwarze@openbsd.org> Cc: Ralph Corderoy <ralph@inputplus.co.uk> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Cc: Dave Kemper <saint.snit@gmail.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-25CONTRIBUTING: Add more information about the mailing listAlejandro Colomar1-9/+20
Put the 'Mailing list' section the first one, since it's the most important, and rewrite it to be more informative (so we don't need to redirect to the website for everything). Also reorganize a little bit around that change. Reported-by: Jakub Wilk <jwilk@jwilk.net> Reported-by: NeilBrown <neilb@suse.de> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-25Revert "Many pages: Document fixed-width types with ISO C naming"Alejandro Colomar31-568/+549
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 Colomar31-549/+568
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-24print_encoding.sh: Remove unused scriptAlejandro Colomar1-47/+0
It considers every page as utf-8, so it doesn't provide any useful information. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-24check_unbalanced_macros.sh: This script's functionality is already covered ↵Alejandro Colomar1-68/+0
by 'make lint-man' Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-24_Generic.3: EXAMPLES: Use a constant expressionAlejandro Colomar1-4/+4
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-24append_COLOPHON.sh, remove_COLOPHON.sh: Remove COLOPHON section.Alejandro Colomar2-66/+0
Users should use their distribution's standard tools to know where a given page comes from and to know how to report a bug. That'll create a small barrier to bug reporters, but that'll hopefully help improve the quality of the reports. It'll also make the pages cleaner, by removing stuff that is obvious to those who know how to use their tools. We still keep part of the information of the COLOPHON, specifically the project name and the version, in the .TH line. Reported-by: Ingo Schwarze <schwarze@openbsd.org> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-24utime.2, utimensat.2: explicitly mention ctime changing.NeilBrown2-0/+5
utime and related calls always change the ctime. It is worth making this explicit. This is clear from the code (vfs_utimes() in fs/utimes.c always sets ATTR_CTIME) and is documented in <https://pubs.opengroup.org/onlinepubs/007904875/functions/utimes.html> Signed-off-by: NeilBrown <neilb@suse.de> Reviewed-by: Jeff Layton <jlayton@kernel.org> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-21_Generic.3: intmax_t can't be intAlejandro Colomar1-1/+0
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
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 Colomar1092-1093/+1093
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-21dist.mk, version.mk: dist: Add version to .THAlejandro Colomar2-4/+42
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com> Cc: Ingo Schwarze <schwarze@openbsd.de> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com>
2022-08-21All pages: Replace the 4th argument to .TH by "Linux man-pages (unreleased)"Alejandro Colomar1096-1096/+1096
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-21_Generic.3: New page documenting _Generic()Alejandro Colomar1-0/+60
Also add a hint of how intmax(3) and other functions using [u]intmax_t types could be better defined by ISO C, by requiring that they're implemented as type-generic macros, to avoid having problems with the ABI. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com> Cc: JeanHeyd Meneide <wg14@soasis.org> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Cc: Ingo Schwarze <schwarze@openbsd.de>
2022-08-21build.mk: clean: Show some outputAlejandro Colomar1-0/+1
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-21fanotify_init.2: srcfixAlejandro Colomar1-1/+2
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-21fanotify_init.2: tfixJakub Wilk1-2/+2
Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-20build-src.mk: Fix appending -Wstrict-prototypesJakub Wilk1-1/+1
Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.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-20tm.3type: tfixJakub Wilk1-2/+2
Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-20timespec.3type: tfixJakub Wilk1-1/+1
Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-20itimerspec.3type: tfixJakub Wilk1-1/+1
Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-20dev_t.3type: tfixJakub Wilk1-1/+1
Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-20clockid_t.3type: tfixJakub Wilk1-1/+1
Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-20memfd_secret.2: tfixJakub Wilk1-1/+1
Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-20landlock_restrict_self.2: tfixJakub Wilk1-1/+1
Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-17clang-tidy/config.yaml: Ignore a useless warningAlejandro Colomar1-0/+1
-readability-identifier-length 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-15getaddrinfo_a.3: actually gnu.cz => gnu.orgнаб1-2/+2
Fixes: a2feb3e14f51a0e74daeb6f0217887ca31799967 ("getaddrinfo_a.3: gnu.cz => gnu.org") Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-15futex.2, futex.7: {ftp://ftp => https://mirrors}.kernel.orgнаб2-2/+2
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-15getaddrinfo_a.3: {ftp.us => mirrors}.kernel.org, likewise for IPнаб1-6/+6
Make the address consistent between 128.30.2.36 (some address in MIT space) and 139.178.88.99 (valid, current) ftp.us.kernel.org EAI_NONAMEs: turn it into mirrors.kernel.org, because the new text uses 139.178.88.99 which is mirrors.kernel.org Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-15mount.2: tfixAlejandro Colomar1-1/+1
Reported-by: glibg10b <pugonfireyt@gmail.com> 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-15proc.5: Document idle state in /proc/pid/statBrett Holman1-0/+3
Signed-off-by: Brett Holman <bholman.devel@gmail.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-15poll.2: tfixŠtěpán Němec1-2/+2
Fixes: 0bdda5d08e82 ("poll.2: Note that poll() equivalent code for ppoll() is not quite equivalent") Signed-off-by: Štěpán Němec <stepnem@gmail.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-15getaddrinfo_a.3: gnu.cz => gnu.orgнаб1-4/+4
gnu.cz exists at a different address (but is unreachable there), and the address we had is an unassigned coolhousing one Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-15getline.3: wfix.enh1-0/+5
Clarify in the RETURN VALUE section that it's necessary to free the buffer, since at least one person missed this up at the start of the DESCRIPTION. Signed-off-by: Elliott Hughes <enh@google.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-15getline.3: srcfix.enh1-8/+8
Signed-off-by: Elliott Hughes <enh@google.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-15nsswitch.conf.5: Mention subid databaseNikola Forró1-0/+9
shadow-utils use nsswitch.conf for configuring delegation of subordinate uids/gids. See also subuid(5) and subgid(5). Link: https://github.com/shadow-maint/shadow/blob/3ec32f9975f262073f8fbdecd2bfaee4a1d3db48/lib/nss.c Signed-off-by: Nikola Forró <nforro@redhat.com> [alx: ffix] Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-15lirc.4: document lirc changes in the kernelSean Young1-26/+31
Linux 5.17 makes LIRC_SET_REC_TIMEOUT_REPORTS an no-op and 5.18 introduces LIRC_OVERFLOW. Also some rewording to clarify. Signed-off-by: Sean Young <sean@mess.org> [alx: ffix] Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-05random.4: tfixAlejandro Colomar1-1/+1
Reported-by: Eric Biggers <ebiggers@kernel.org> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-05random.4: Update description about O_NONBLOCK flagGUO Zihua1-1/+6
The O_NONBLOCK flag has been ignored since Linux 5.6 and this patch states this change in man page. The commit that introduced this change in the Linux kernel is 30c08efec888 ("random: make /dev/random be almost like /dev/urandom") Signed-off-by: GUO Zihua <guozihua@huawei.com> Reviewed-by: Petr Vorel <pvorel@suse.cz> Cc: Florian Weimer <fweimer@redhat.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-02iovec.3type, regex_t.3type: srcfixAlejandro Colomar2-3/+3
mandoc: man3type/iovec.3type:19:14: STYLE: unterminated quoted argument mandoc: man3type/regex_t.3type:23:28: STYLE: unterminated quoted argument mandoc: man3type/regex_t.3type:25:28: STYLE: unterminated quoted argument Reported-by: 'make lint-man' Reported-by: mandoc(1) Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-02argz_add.3: srcfixAlejandro Colomar1-1/+1
mandoc: man3/argz_add.3:20:77: STYLE: unterminated quoted argument Reported-by: 'make lint-man' Reported-by: mandoc(1) Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-02fanotify_init.2, mount_setattr.2: ffixAlejandro Colomar2-2/+0
mandoc: man2/fanotify_init.2:332:2: WARNING: skipping paragraph macro: PP empty mandoc: man2/mount_setattr.2:677:2: WARNING: skipping paragraph macro: PP empty Reported-by: 'make lint-man' Reported-by: mandoc(1) Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-02getgrent_r.3, psignal.3: ffixAlejandro Colomar2-0/+4
Reported-by: 'make lint-man' Reported-by: groff(1) Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-02ioctl_userfaultfd.2, fanotify.7: ffixAlejandro Colomar2-2/+2
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-02proc.5: ffixAlejandro Colomar1-58/+68
an.tmac:man5/proc.5:2010: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2011: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2012: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2013: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2014: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2015: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2016: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2017: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2018: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2019: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2020: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2021: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2022: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2023: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2024: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2025: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2026: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2027: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2028: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2029: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2030: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2031: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2032: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2033: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2034: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2035: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2036: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2037: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2038: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2039: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2040: style: 4 leading space(s) on input line an.tmac:man5/proc.5:2041: style: 4 leading space(s) on input line an.tmac:man5/proc.5:3332: style: 5 leading space(s) on input line an.tmac:man5/proc.5:3333: style: 5 leading space(s) on input line an.tmac:man5/proc.5:3334: style: 5 leading space(s) on input line an.tmac:man5/proc.5:3335: style: 5 leading space(s) on input line an.tmac:man5/proc.5:3336: style: 5 leading space(s) on input line an.tmac:man5/proc.5:3337: style: 5 leading space(s) on input line an.tmac:man5/proc.5:3338: style: 5 leading space(s) on input line an.tmac:man5/proc.5:3339: style: 5 leading space(s) on input line an.tmac:man5/proc.5:3340: style: 5 leading space(s) on input line an.tmac:man5/proc.5:3341: style: 5 leading space(s) on input line an.tmac:man5/proc.5:3342: style: 4 leading space(s) on input line an.tmac:man5/proc.5:3343: style: 4 leading space(s) on input line an.tmac:man5/proc.5:3344: style: 4 leading space(s) on input line an.tmac:man5/proc.5:3345: style: 4 leading space(s) on input line an.tmac:man5/proc.5:3346: style: 4 leading space(s) on input line an.tmac:man5/proc.5:3347: style: 4 leading space(s) on input line an.tmac:man5/proc.5:3348: style: 4 leading space(s) on input line an.tmac:man5/proc.5:3349: style: 4 leading space(s) on input line an.tmac:man5/proc.5:3350: style: 4 leading space(s) on input line an.tmac:man5/proc.5:3351: style: 4 leading space(s) on input line an.tmac:man5/proc.5:3352: style: 4 leading space(s) on input line an.tmac:man5/proc.5:3353: style: 4 leading space(s) on input line an.tmac:man5/proc.5:3354: style: 4 leading space(s) on input line an.tmac:man5/proc.5:3355: style: 4 leading space(s) on input line an.tmac:man5/proc.5:3357: style: 4 leading space(s) on input line an.tmac:man5/proc.5:3359: 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-01st.4: ffixAlejandro Colomar1-22/+26
an.tmac:man4/st.4:715: style: use of deprecated macro: .HP an.tmac:man4/st.4:721: style: use of deprecated macro: .HP an.tmac:man4/st.4:727: style: use of deprecated macro: .HP an.tmac:man4/st.4:730: style: use of deprecated macro: .HP an.tmac:man4/st.4:736: style: use of deprecated macro: .HP an.tmac:man4/st.4:739: style: use of deprecated macro: .HP an.tmac:man4/st.4:744: style: use of deprecated macro: .HP an.tmac:man4/st.4:749: style: use of deprecated macro: .HP an.tmac:man4/st.4:753: style: use of deprecated macro: .HP an.tmac:man4/st.4:756: style: use of deprecated macro: .HP an.tmac:man4/st.4:764: style: use of deprecated macro: .HP Reported-by: 'make lint-man' Reported-by: groff(1) Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-01console_codes.4: ffixAlejandro Colomar1-31/+51
Reformat .HP paragraphs with .TP and .TQ. an.tmac:man4/console_codes.4:89: style: use of deprecated macro: .HP an.tmac:man4/console_codes.4:91: style: use of deprecated macro: .HP an.tmac:man4/console_codes.4:94: style: use of deprecated macro: .HP an.tmac:man4/console_codes.4:97: style: use of deprecated macro: .HP an.tmac:man4/console_codes.4:101: style: use of deprecated macro: .HP an.tmac:man4/console_codes.4:103: style: use of deprecated macro: .HP an.tmac:man4/console_codes.4:105: style: use of deprecated macro: .HP an.tmac:man4/console_codes.4:107: style: use of deprecated macro: .HP an.tmac:man4/console_codes.4:109: style: use of deprecated macro: .HP an.tmac:man4/console_codes.4:111: style: use of deprecated macro: .HP an.tmac:man4/console_codes.4:113: style: use of deprecated macro: .HP an.tmac:man4/console_codes.4:604: style: use of deprecated macro: .HP an.tmac:man4/console_codes.4:606: style: use of deprecated macro: .HP an.tmac:man4/console_codes.4:608: style: use of deprecated macro: .HP an.tmac:man4/console_codes.4:610: style: use of deprecated macro: .HP Reported-by: 'make lint-man' Reported-by: groff(1) Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-01cciss.4: ffixAlejandro Colomar1-11/+14
an.tmac:man4/cciss.4:100: style: 4 leading space(s) on input line an.tmac:man4/cciss.4:101: style: 4 leading space(s) on input line an.tmac:man4/cciss.4:102: style: 4 leading space(s) on input line an.tmac:man4/cciss.4:103: style: 4 leading space(s) on input line an.tmac:man4/cciss.4:104: style: 4 leading space(s) on input line an.tmac:man4/cciss.4:105: style: 4 leading space(s) on input line an.tmac:man4/cciss.4:106: style: 4 leading space(s) on input line an.tmac:man4/cciss.4:107: style: 4 leading space(s) on input line an.tmac:man4/cciss.4:281: 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-01__setfpucw.3: ffixAlejandro Colomar1-3/+10
an.tmac:man3/__setfpucw.3:58: style: 5 leading space(s) on input line an.tmac:man3/__setfpucw.3:59: style: 5 leading space(s) on input line an.tmac:man3/__setfpucw.3:60: style: 5 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-01__setfpucw.3: pfixAlejandro Colomar1-3/+3
\- is unnecessary here. As a list enumerator, any character is good. Simplify. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-01membarrier.2: ffixAlejandro Colomar1-4/+9
Format the table using tbl(1), to fix the following warnings. an.tmac:man2/membarrier.2:222: style: 23 leading space(s) on input line an.tmac:man2/membarrier.2:223: style: 7 leading space(s) on input line an.tmac:man2/membarrier.2:224: style: 7 leading space(s) on input line an.tmac:man2/membarrier.2:225: style: 7 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-01getrlimit.2: srcfixAlejandro Colomar1-12/+18
an.tmac:man2/getrlimit.2:246: 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-01getrlimit.2: Use MIN(3)Alejandro Colomar1-1/+1
min() doesn't exist, but MIN(3) exists. Use it. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-01chown.2: srcfixAlejandro Colomar1-3/+3
Reported-by: 'make lint-man' Reported-by: groff(1) Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-01timer_settime.2, timerfd_create.2, itimerspec.3type: Document itimerspec in ↵Alejandro Colomar3-23/+37
a new page Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-01ioctl_ns.2: EXAMPLES: Add missing includeAlejandro Colomar1-6/+1
Instead of redefining stuff, add the necessary header. Reported-by: 'make lint-c' Reported-by: iwyu(1) Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-01byteorder.3: STANDARDS: SimplifyAlejandro Colomar1-5/+0
No current systems require the inclusion of <netinet/in.h> anymore. POSIX.1-2001 has been around for more than 20 years, so let's simplify. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-01bind.2, process_vm_readv.2: EXAMPLES: Add necessary includes and ftm(7)Alejandro Colomar2-0/+2
Reported-by: 'make lint-c' Reported-by: clang(1) Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-01.checkpatch.conf, CPPLINT.cfg: Ignore some warnings from 'make lint-c'Alejandro Colomar2-1/+2
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-01Various pages: EXAMPLES: tfixAlejandro Colomar5-22/+22
Use escape sequences that produce the correct output, suitable for copy&paste into real C programs. Reported-by: 'make lint-c' 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-08-01poll.2: 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-01sigaction.2: 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-01syslog.2: 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-01mremap.2: wfixŠ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-01getrlimit.2: tfixŠtěpán Němec1-2/+2
Signed-off-by: Štěpán Němec <stepnem@gmail.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-01Makefile: Disable builtin rules and variablesAlejandro Colomar1-0/+2
We don't use them at all, so by disabling them, the debug output of make(1) will be smaller. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-01Makefile, src.mk, *.mk: Move some definitions to a helper MakefileAlejandro Colomar8-11/+33
To be able to explicitly include the file with the definitions, wherever it is needed. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-01Makefile, cmd.mk, *.mk: Allow using different names for basic commandsAlejandro Colomar8-28/+68
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-01dist.mk: Create tarballs with a top-level directoryAlejandro Colomar1-1/+2
Need to use a trick with sed(1) to avoid tar(1) modifying the symlinks. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-01README: man0 is not used anymoreAlejandro Colomar1-1/+1
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-30sa_family_t.3type, sockaddr.3type: Document sa_family_tAlejandro Colomar2-0/+12
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-30sockaddr.3type, timer_t.3type, void.3type: wfixAlejandro Colomar3-11/+6
Replace "shall" wordings by simpler text, to not resemble a standards document. When saying something like "According to POSIX/ISO C, ...", if the mentioned standard is the same one described in STANDARDS, remove that text (it is redundant). However, if ISO C is the main standard that describes a type, but POSIX applies further restrictions, keep that text. Remove pedantic notes that may only be interesting to compiler writers. Reported-by: Ingo Schwarze <schwarze@openbsd.org> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-30ptrdiff_t.3type, size_t.3type, time_t.3type, va_list.3type, void.3type: ffixAlejandro Colomar5-8/+6
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-29Various pages: wfixAlejandro Colomar17-71/+28
Replace "shall" wordings by simpler text, to not resemble a standards document. When saying something like "According to POSIX/ISO C, ...", if the mentioned standard is the same one described in STANDARDS, remove that text (it is redundant). However, if ISO C is the main standard that describes a type, but POSIX applies further restrictions, keep that text. Remove pedantic notes that may only be interesting to compiler writers. Reported-by: Ingo Schwarze <schwarze@openbsd.org> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-29sysexits.h.3head: Add LIBRARY sectionAlejandro Colomar1-0/+3
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-29Makefile, install-man.mk: Support man3head, and remove support for man0Alejandro Colomar2-9/+9
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-29sysexits.h.3head: Move header page to a new man3head sectionAlejandro Colomar1-17/+79
Use man3head, as other Unix systems already use. As Ingo said, man0 is not the right place for header files. Also, this patch does some changes to the page itself: Expand the SYNOPSIS to have together all of the values. Also, add a small comment about the constant (taken from the header file). Link: <https://lore.kernel.org/linux-man/11110a04-f96b-0d32-53e3-adcce618c543@gmail.com/> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Cc: Ingo Schwarze <schwarze@openbsd.org> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-29getrlimit.2: RLIMIT_NPROC also ignored for ruid 0Robert Schneider1-1/+2
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-29Many pages: Use STANDARDS instead of CONFORMING TOAlejandro Colomar900-903/+903
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-29getsid.2: deduplicate getsid(0) caseнаб1-2/+0
The first sentence in getsid(0) returns the session ID of the calling process. getsid() returns the session ID of the process with process ID pid. If pid is 0, getsid() returns the session ID of the calling process. blames to beginning of git, duplicates the third one, and doesn't stylistically match current formatting Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> 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-26strsignal.3: fix str(d)abbrev typoнаб1-2/+2
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> 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-22size_t.3type: tfixAlejandro Colomar1-1/+1
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 Colomar4-82/+64
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 Colomar2-141/+160
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-22bash_aliases: man_gitstaged(): Never show dirsAlejandro Colomar1-3/+3
Directories are obvious also for scripts, or other non-man(7) files. Also, this adds support for man3type and man2type pages. 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 Colomar2-23/+34
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-21Makefile: Remove unused variablesAlejandro Colomar1-13/+2
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-21Many pages: Use man3type/ and man2type/ for type pagesAlejandro Colomar112-121/+135
Quoting Ingo: [ The mandoc(1) program is also able to handle paths like "man3/id_t.3type". It will consider that page to be *both* in section "3" (as specified by the directory name) and in section "3type" (as specified by the file name and by the .TH macro). I would consider it better style to keep section names consistent, i.e. to use either "man3/id_t.3" .TH id_t 3 or "man3type/id_t.3type" .TH id_t 3type, but it's not a big deal: since many systems (in particular various Linux distros) suffer from such inconsistencies, handling such inconsistencies gracefully is an important feature that certainly won't get removed. ] Let's be nice, and do things right here, in the hope that others may follow the example. === Most of this patch has been scripted: $ mkdir man2type man3type $ find man2 | grep type$ | while read f; do mv -t man2type $f; done $ find man3 | grep type$ | while read f; do mv -t man3type $f; done $ grep -rl man3/.*type man* | xargs sed -i 's,man3/,man3type/,' Apart from that, I adapted the Makefiles, and moved va_list into the man3type subsection (it was accidentally placed in the main 3 section). Link: <https://lore.kernel.org/linux-man/YrB66rgFZqryrmpt@asta-kit.de/T/#u> Reported-by: Ingo Schwarze <schwarze@usta.de> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-21timespec.3type, system_data_types.7: Move timespec to a separate pageAlejandro Colomar2-65/+74
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-21timeval.3type, system_data_types.7: Move timeval to a separate pageAlejandro Colomar2-32/+41
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 Colomar2-31/+43
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-21MAINTAINER_NOTES: Update references about generation of bpf-helpers.7Alejandro Colomar1-2/+1
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 Colomar3-74/+76
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 Colomar4-98/+115
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, size_t.3type, ssize_t.3type: Merge size_t and ssize_t into ↵Alejandro Colomar3-93/+90
a single page Since ssize_t is just the signed version of size_t, it makes sense to document them together. 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 Colomar2-40/+50
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 Colomar2-103/+107
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-20id_t.3type: wfixAlejandro Colomar1-1/+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 Colomar4-88/+93
and off64_t to separate page, and document loff_t Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-20strftime.3, strftime_l.3: mention strftime_l() with .so linkнаб2-1/+26
POSIX.1-2008 TC2: > [CX] The strftime_l() function shall be equivalent to the strftime() function, except that the locale data used is from the locale represented by locale. > [CX] The behavior is undefined if the locale argument to strftime_l() is the special locale object LC_GLOBAL_LOCALE or is not a valid locale object handle. Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-20ctime.3: remove struct tm vestigiaнаб1-15/+0
struct tm now lives in tm.3type, and we describe both of these fields, in detail and correctly, therein Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-20tm.3type: describe tm_zone, tm_gmtoffнаб1-0/+51
FreeBSD timezone(3) is V7 char *timezone(int zone, int dst), our documentation would imply it's impossible to service this type of system portably Indeed, glibc defines them both, and they make more sense for most use-cases than trying to use the globals glibc cited for __USE_MISC, tm_zone invalidation is Debian 2.33-7 POSIX cited for XSI marking is Issue 7 TC2 CSRG CD #2 contains 4.3BSD-Tahoe with both members We currently ship an outdated (and factually misleading) version of this description in ctime.3 Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-19tm.3type: srcfixAlejandro Colomar1-1/+2
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-19tm.3type: widen member alignment to take up to const char *наб1-9/+9
This lets us take const char *tm_zone. Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-19tm.3type: align rangesнаб1-6/+6
This, to me, makes these much more readable Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-19printf.3: Note about thousands grouping and the C localeDr. Jürgen Sauermann1-0/+5
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-19tm.3type: tm_year is year minus 1900, not sinceнаб1-1/+1
Since only makes sense if the year represented is after 1900: how many years have passed since 1900 in... 1410? Also \fB the constant like elsewhere in the hunk Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-19tm.3type: tfixнаб1-1/+1
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-18bind.2: EXAMPLES: Add cleanup codeAlejandro Colomar1-2/+5
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-10man-pages-5.14.lsm: Update format and maintainersAlejandro Colomar1-2/+3
The file is compatible with the newer Begin4 format, so specify it. Add myself to 'Maintained-by:'. Link: <https://lsm.qqx.org/> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-10CONTRIBUTING, README: Move info from the README to CONTRIBUTINGAlejandro Colomar2-15/+24
Also, write file name in <>. Also, update the README, to say sections 0 through 8. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-10Makefile, README, INSTALL: Improve INSTALL documentationAlejandro Colomar3-17/+79
Add a 'make help' target to document the features of our Makefile. Move all documentation about installing from the README to a new INSTALL file, following GNU coding standards. See <https://www.gnu.org/prep/standards/html_node/Releases.html#Releases>. INSTALL contains minimal information, and defers to 'make help' for the rest. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-10install.mk, lint.mk: Add comment to endifAlejandro Colomar2-2/+2
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-10Makefile: srcfixAlejandro Colomar1-8/+4
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-10Makefile, install.mk, install-html.mk, install-man.mk: install: split into ↵Alejandro Colomar4-37/+56
helper Makefile Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-10Makefile, build.mk, build-html.mk, build-src.mk, dist.mk, lint.mk, ↵Alejandro Colomar6-19/+59
lint-man.mk: build, clean: split into helper Makefile Add a new 'build' target (alias for 'all'), for consistency. Also, use MKDIR instead of INSTALL_DIR to create directories in $(builddir). Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-10Makefile, lint.mk, build-src.mk, lint-c.mk, lint-man.mk: lint: split into ↵Alejandro Colomar5-38/+58
helper Makefile Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-10Makefile, install-man.mk: install-man: split into helper MakefileAlejandro Colomar2-107/+123
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-10Makefile, build-html.mk, install-html.mk: build-html: split into helper MakefileAlejandro Colomar3-32/+48
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-10Makefile, install-html.mk: install-html: split into helper MakefileAlejandro Colomar2-27/+44
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-10Makefile, dist.mk: dist: split into helper MakefileAlejandro Colomar2-41/+50
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-10Makefile, build-src.mk, lint-c.mk: build-src: split into helper MakefileAlejandro Colomar3-97/+115
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-10Makefile, lint-man.mk: lint-man: split into helper MakefileAlejandro Colomar2-49/+64
Also renamed part of the files s/lint.man/lint-man/ Also updated copyright year. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-10Makefile, lint-c.mk: lint-c: split into helper MakefileAlejandro Colomar2-68/+82
Also renamed part of the files s/lint.c/lint-c/ Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-10Makefile: rename targets that build examplesAlejandro Colomar1-20/+23
Use 'build-src' as a prefix, to improve the organization. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-10Makefile: subdivide 'lint' into 'lint-c' and 'lint-man'Alejandro Colomar1-18/+45
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-07statx.2: correctly document STATX_ALLEric Biggers1-1/+2
Since kernel commit 581701b7efd6 ("uapi: deprecate STATX_ALL"), STATX_ALL is deprecated. It doesn't include STATX_MNT_ID, and it won't include any future flags. Update the man page accordingly. Signed-off-by: Eric Biggers <ebiggers@google.com> Reviewed-by: Andreas Dilger <adilger@dilger.ca> Reviewed-by: Darrick J. Wong <djwong@kernel.org> [alx: wfix, ffix] Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-05fts.3: tfixнаб1-2/+2
statp -> fts_statp Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-05fts.3: list primary modes firstнаб1-21/+21
FTS_LOGICAL sorts before FTS_PHYSICAL, FTS_COMFOLLOW modifies FTS_PHYSICAL, the remaining flags follow in sorted order Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-05fts.3: clarify FTS_COMFOLLOW behaviourнаб1-3/+3
FTS_COMFOLLOW is equivalent to FTS_LOGICAL for fts_level == 0: define it as such Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-05fts.3: remove triplicate requirement spielнаб1-16/+0
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-05fts.3: note that lstat(2) may also provide fts_statpнаб1-7/+18
In FTS_PHYSICAL mode, it's always lstat() In FTS_LOGICAL mode, it's stat() unless it ENOENTs in which case it's lstat() In FTS_PHYSICAL | FTS_COMFOLLOW mode, it's FTS_LOGICAL for path_argv and FTS_PHYSICAL for children Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-04fts.3: wfixнаб1-2/+1
This list consistently uses "this option", force that for FTS_NOCHDIR too Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-04fanotify.7, fanotify_init.2, fanotify_mark.2: Document FAN_RENAMEAmir Goldstein3-7/+47
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 Goldstein3-17/+68
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-03getdate.3: EXAMPLES: Fix comment.Alejandro Colomar1-2/+2
The comments were misplaced (interchanged). strptime(3): %a or %A The name of the day of the week according to the current locale, in abbreviated form or the full name. %T Equivalent to %H:%M:%S. %F Equivalent to %Y-%m-%d, the ISO 8601 date format. Reported-by: <pellucida@tutanota.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-03getmntent.3: wfixAlejandro Colomar1-3/+4
Reported-by: Lucien Gentis <lucien.gentis@waika9.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-07-03updwtmp.3: Add #define GNU_SOURCE for updwtmpxSam James1-0/+1
Closes: https://bugzilla.kernel.org/show_bug.cgi?id=216168 Signed-off-by: Sam James <sam@gentoo.org> 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-20epoll_event.3type: NAME: Add epoll_data and epoll_data_tAlejandro Colomar1-1/+1
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-20epoll_ctl.2, epoll_wait.2: Defer definition of epoll_event to epoll_event(3type)Alejandro Colomar2-34/+4
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-20epoll_data.3type, epoll_data_t.3type: Add links to epoll_event.3typeAlejandro Colomar2-0/+2
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-20epoll_event.3type: Add new page documenting 'struct epoll_event'Alejandro Colomar1-0/+55
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-20aiocb.3type, lconv.3type: NAME: Remove 'struct' keywordAlejandro Colomar2-2/+2
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-20aiocb.3type, lconv.3type: .TH: tfixAlejandro Colomar2-2/+2
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-20Makefile, README: Fix make allAlejandro Colomar2-6/+1
`make all` should not install and even less uninstall. That's unintuitive, and might break stuff that we don't want to break. Instead, make it build all useful things that we can build, which right now is only the HTML pages, but in the future might include PDF pages. Reported-by: Ingo Schwarze <schwarze@usta.de> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-19Makefile: SHELL: Use a portable bashAlejandro Colomar1-1/+1
Reported-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: 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 Colomar2-91/+97
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-17tm.3type: wfixAlejandro Colomar1-1/+1
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-17intN_t.3type: ffixAlejandro Colomar1-3/+3
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-17fanotify.7, fanotify_mark.2: Document FAN_FS_ERRORGabriel Krisman Bertazi2-0/+101
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-17process_madvise.2: wfixAlejandro Colomar1-2/+2
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-17Various pages: Defer definition of iovec to iovec(3type)Alejandro Colomar6-71/+10
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-17iovec.3type: Add new page documenting 'struct iovec'Alejandro Colomar1-0/+47
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-16openat2.2, open_how.2type, Makefile: Add new page documenting 'struct open_how'Alejandro Colomar3-13/+62
Simplify openat2(2) a little bit, but without removing information that is crucial to openat2(2). Adapt the Makefile to accept the 2type section. Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-16ctime.3, strptime.3, time.7: Refer to tm(3type)Alejandro Colomar3-77/+7
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-06-16tm.3type: Add new page documenting 'struct tm'Alejandro Colomar1-0/+59
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-15uname.2: deweirdifyнаб1-37/+12
The NOTES were not only weirdly reductionist, but also highly opinionated in the wrong direction. Yes, it's a syscall in SysIII; not in 4.4BSD. Well, in general, it exists in 4.4BSD for obvious conformace reasons. No, it doesn't "know" (and if it does, that's not relevant), historically and practically this is the broad CPU/machine type (compare uname -p on SysVr4 (=> SunOS 5 => NetBSD), which is the actual CPU model (usually)). Everywhere, ex. def., the nodename is what the BSD calls the hostname. "No standard" also speaks of sethostname(), so. Historical precedent (i.e. all implementations, save *maybe* for weirdo XENIX, who cares about weirdo XENIX) defines the hostname to be uname -n (indeed, SVr3 uname -S sets /both/ nodename /and/ sysname! that's not relevant here; SunOS gets it from the network (unless configured manually)). Someone clearly cited SysVr4's "Internet hostnames" comment w/o credit; fix that. 8-byte truncation is really quite secondary here (indeed, that's what SysVr4 does for pre-SysVr4 uname() callers that haven't been rebuilt. you will never encounter it). The hostname is not meaningless, obviously?? Also fix machine to say "hardware type", like the standard; "hardware identifier" would be hostid. I wrote six seething pages about hostid, and machine is /not/ hostid. Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-15uname.2: fix standard reference wordingнаб1-5/+6
Issue 6: IEEE Std 1003.1-2001/Cor 2-2004, item XBD/TC2/D6/27 is applied, changing the description of nodename within the utsname structure from ``an implementation-defined communications network'' to ``the communications network to which this node is attached, if any''. Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-15Many pages: Move type pages to subsection 3typeAlejandro Colomar95-70/+71
These pages are not exactly what man3 typically contains, which is library functions. Instead, types fit better in a subsection of man3, and some UNIX systems have already a section 3type, so let's use the same name. Adapt the Makefile to work with this subsection. Except for the Makefile, these changes are scripted. Scripted changes: $ find man3 -type f \ | grep '_t\.3$' \ | while read f; do mv $f ${f}type; done; $ find man? -type f \ | xargs grep -l '^\.so.*_t\.3' \ | xargs sed -i '/^\.so/s/\.3$/\.3type/'; $ find man? -type f \ | xargs grep -l '^\.BR .*_t (3)' \ | xargs sed -i '/^\.BR .*_t (3)/s/3)/3type)/'; $ find man? -type f \ | grep -- '-struct\.[23]$' \ | while read f; do g="$(echo $f | sed 's/-struct//')"type; mv $f $g; done; $ find man? -type f \ | xargs grep -l '^\.so.*-struct\.[23]' \ | xargs sed -i -e '/^\.so/s/-struct//' -e '/^\.so/s/$/type/'; $ find man? -type f \ | xargs grep -l '^\.BR .*-struct (.)' \ | xargs sed -i -e '/^\.BR .*-struct (.)/s/\([23]\)/\1type/' \ -e '/^\.BR .*-struct /s/-struct//'; $ find man? -type f \ | grep -- '-union\.[23]$' \ | while read f; do g="$(echo $f | sed 's/-union//')"type; mv $f $g; done; $ find man? -type f \ | grep '3type' \ | xargs sed -i '/^\.TH/s/ 3 / 3type /'; Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-15userfaultfd.2: Minor tweaks to Peter's patchesAlejandro Colomar1-7/+8
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com> Cc: Peter Xu <peterx@redhat.com>
2022-06-15userfaultfd.2: Update on write-protection supportPeter Xu1-3/+6
The shmem/hugetlbfs memory types are supported for write-protection messages very lately. Update the man page to reflect that. Signed-off-by: Peter Xu <peterx@redhat.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-15userfaultfd.2: Add section for UFFD_USER_MODE_ONLYPeter Xu1-2/+12
Add a paragraph for UFFD_USER_MODE_ONLY flag that was introduced in Linux 5.11. Signed-off-by: Peter Xu <peterx@redhat.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-10madvise.2: Clarify addr/length and update hugetlb supportMike Kravetz1-9/+23
Clarify that madvise only works on full pages, and remove references to 'bytes'. Update MADV_DONTNEED and MADV_REMOVE sections to remove notes that HugeTLB mappings are not supported. Indicate the releases when they were first supported as well as alignment restrictions. Signed-off-by: Mike Kravetz <mike.kravetz@oracle.com> Acked-by: Peter Xu <peterx@redhat.com> [alx: wsfix] Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-09statx.2: Add #define _GNU_SOURCE to synopsisJakub Wilk1-10/+1
The original text hinted that you need _GNU_SOURCE only for a few of the AT_* constants; but actually you need it to get the statx() declaration. [alx:] You can check yourself: $ grepc -tfp statx ./io/bits/statx-generic.h:60: int statx (int __dirfd, const char *__restrict __path, int __flags, unsigned int __mask, struct statx *__restrict __buf) __THROW __nonnull ((2, 5)); $ grep -rnC1 '<bits/statx-generic.h>' io/ io/bits/statx-generic.h-21-#ifndef _SYS_STAT_H io/bits/statx-generic.h:22:# error Never include <bits/statx-generic.h> directly, include <sys/stat.h> instead. io/bits/statx-generic.h-23-#endif -- io/bits/statx.h-25-/* Use the generic definitions. */ io/bits/statx.h:26:#include <bits/statx-generic.h> $ grep -rnC1 '<bits/statx.h>' io/ io/bits/statx.h-21-#ifndef _SYS_STAT_H io/bits/statx.h:22:# error Never include <bits/statx.h> directly, include <sys/stat.h> instead. io/bits/statx.h-23-#endif -- io/sys/stat.h-371-#ifdef __USE_GNU io/sys/stat.h:372:# include <bits/statx.h> io/sys/stat.h-373-#endif Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-09Changes.old: tfixJakub Wilk1-2/+2
Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-08mount_setattr.2: Minor tweaks to Christian's patch setAlejandro Colomar1-6/+6
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-06-08mount_setattr.2: ffixChristian Brauner1-1/+1
Fix a typo in my name. Signed-off-by: Christian Brauner (Microsoft) <brauner@kernel.org> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>