aboutsummaryrefslogtreecommitdiffstats
path: root/man5
AgeCommit message (Collapse)AuthorFilesLines
2024-05-02man/, share/mk/: Move man*/ to man/Alejandro Colomar159-18440/+1
This is a scripted change: $ mkdir man/; $ mv man* man/; $ ln -st . man/man*; $ find share/mk/ -type f \ | xargs grep -l '^MANDIR *:=' \ | xargs sed -i '/^MANDIR *:=/s,$,/man,'; $ find share/mk/dist/ -type f \ | xargs grep -l man \ | xargs sed -i 's,man%,man/%,g'; Link: <https://lore.kernel.org/linux-man/YxcV4h+Xn7cd6+q2@pevik/T/> Cc: Petr Vorel <pvorel@suse.cz> Cc: Jakub Wilk <jwilk@jwilk.net> Cc: Stefan Puiu <stefan.puiu@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-04-14proc.5: Refer to split-out manual pages for detailed descriptionSalvatore Bonaccorso1-1/+3
Back in August 2023 various parts of proc(5) were split out into separate manpages. The final cleanup in 92cdcec79df0 ("proc.5: Clean up after making sashimi of this page") missed to as well refer to the split out manpages and retained the wording that details are found further below in the manpages for the various files. Fixes: 92cdcec79df0 ("proc.5: Clean up after making sashimi of this page") Signed-off-by: Salvatore Bonaccorso <carnil@debian.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-18proc_pid_io.5: Move note to CAVEATSAlejandro Colomar1-6/+5
Cc: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-17proc_pid_io.5: Dewafflifyнаб1-37/+31
This page copies verbatim the contents of Documentation/filesystems/proc.rst, added wholesale in commit f9c99463b0cd05603d125c915e2886d55a686b82 ("[PATCH] Documentation for io-accounting / reporting via procfs") in 2007. As such, it mirrors the sensibilities of the time ‒ writing "successful read returns" as "data pulled from storage. actually just the data the process gave to read(). this also means from non-regular files! whether the data was pulled from storage doesn't matter actually (obligatory cache mention)" for the modern reader this is just a lot of waffling (note also that processes give no data to read()!) ‒ and sensibilities of the sheepish implementer in kernel documentation ‒ "an attempt" for a well-defined kernel behaviour, mentioning the "current implementation", consistent mentions of specific kernel-internal caching mechanisms, "the big inaccuracy here". Re-write to be more useful and less misleading as documentation; the syscall enumeration is accurate for kernel v6.8, but the sysc? stats are also bumped by kernel_{read,write}(), which is sometimes used by too many syscalls in too many scenarios to usefully enumerate. Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-17proc_pid_io.5: Stats include childrenнаб1-9/+18
This file is like getrusage(2) RUSAGE_SELF + RUSAGE_CHILDREN, the current wording implies it's like just RUSAGE_SELF. Compare: #include <fcntl.h> #include <signal.h> #include <string.h> #include <sys/wait.h> #include <unistd.h> void copy() { char buf[1024]; int fd = open("/proc/self/io", 0); write(1, buf, read(fd, buf, sizeof(buf))); close(fd); } int main() { copy(); copy(); if (!fork()) { zero:; int fd = open("/dev/zero", 0); char buf[64 * 1024] = {}; write(1, buf, 10000); for (int i = 0; i < 1000; ++i) read(fd, buf, sizeof(buf)); _exit(0); } sleep(1); copy(); wait(NULL); copy(); signal(SIGCHLD, SIG_IGN); if (!fork()) goto zero; sleep(1); copy(); wait(NULL); copy(); } yielding rchar: 3980 wchar: 0 syscr: 9 syscw: 0 read_bytes: 2968 write_bytes: 0 cancelled_write_bytes: 0 rchar: 4076 wchar: 96 syscr: 10 syscw: 1 read_bytes: 2968 write_bytes: 96 cancelled_write_bytes: 0 rchar: 4175 wchar: 195 syscr: 11 syscw: 2 read_bytes: 2968 write_bytes: 195 cancelled_write_bytes: 0 rchar: 65540276 wchar: 10296 syscr: 1012 syscw: 4 read_bytes: 2968 write_bytes: 10296 cancelled_write_bytes: 0 rchar: 65540387 wchar: 10407 syscr: 1013 syscw: 5 read_bytes: 2968 write_bytes: 10407 cancelled_write_bytes: 0 rchar: 65540498 wchar: 10518 syscr: 1014 syscw: 6 read_bytes: 2968 write_bytes: 10518 cancelled_write_bytes: 0 Just s/process/& and its waited-for children/ but re-broken per review. Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-17tzfile.5: ffixAlejandro Colomar1-2/+2
Cc: "G. Branden Robinson" <branden@debian.org> Cc: Paul Eggert <eggert@cs.ucla.edu> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-17tzfile.5: Avoid crashing man2html(1)Alejandro Colomar1-14/+14
Link: <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067022> Cc: Paul Eggert <eggert@cs.ucla.edu> Cc: "G. Branden Robinson" <branden@debian.org> Cc: Robert Luberda <robert@debian.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-16tzfile.5, tzselect.8, zdump.8, zic.8: Refresh pagesAlejandro Colomar1-66/+78
Refreshed from tzdb-2024a. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-14getrusage.2, proc_pid_io.5: Crosslinkнаб1-0/+1
These serve the same purpose from different perspectives. Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-14proc_pid_io.5: Mention atomicity in atomicity noteнаб1-5/+4
And drop "current implementation" (wording still literal from Documentation/filesystems/proc.rst). Of course this describes the current implementation. Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-03-14proc_pid_io.5: wfixнаб1-4/+4
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-02-25man*/: ffixAlejandro Colomar3-3/+3
Found with: $ grep -rn '^\.[BI] .* [.,:;)]*$' man* man2/prctl.2:382:.B FR=1 . man2/openat2.2:377:.B EAGAIN . man2/openat2.2:424:.I how.resolve . man5/elf.5:788:.B PF_R . man5/networks.5:18:.I name number aliases ... man5/protocols.5:31:.I protocol number aliases ... man7/cgroups.7:980:.I """max""" . Cc: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-01-28man*/: Say ISO 3166Alejandro Colomar1-3/+3
Link: <https://www.iso.org/iso-3166-country-codes.html> Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-01-28locale.5: Say ISO 4217Alejandro Colomar1-1/+1
Link: <https://www.iso.org/standard/64758.html> Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-01-28man*/: Say ISO 639Alejandro Colomar1-3/+3
Link: <https://www.iso.org/standard/74575.html> Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-01-28filesystems.5: Say ISO/IEC 9660Alejandro Colomar1-2/+2
Link: <https://www.iso.org/standard/81979.html> Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-01-28man*/: Say ISO/IEC 6429Alejandro Colomar1-9/+9
Link: <https://www.iso.org/standard/12782.html> Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-01-28man*/: Say ISO/IEC 8859Alejandro Colomar1-1/+1
Link: <https://www.iso.org/standard/28245.html> Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2024-01-15locale.5: tfixG. Branden Robinson1-1/+1
...that proved surprisingly tough to troubleshoot. I got the following output from my working copy. grotty:...:(man5/locale.5):32291: error: output above first line discarded grotty:...:(man5/locale.5):32291: error: output above first line discarded grotty:...:(man5/locale.5):32291: error: output above first line discarded grotty:...:(man5/locale.5):32291: error: output above first line discarded grotty:...:(man5/locale.5):32291: error: output above first line discarded grotty:...:(man5/locale.5):32291: error: output above first line discarded grotty:...:(man5/locale.5):32291: error: output above first line discarded grotty:...:(man5/locale.5):32291: error: output above first line discarded grotty:...:(man5/locale.5):32291: error: output above first line discarded grotty:...:(man5/locale.5):32292: error: output above first line discarded grotty:...:(man5/locale.5):32294: error: output above first line discarded grotty:...:(man5/locale.5):32294: error: output above first line discarded grotty:...:(man5/locale.5):32294: error: output above first line discarded grotty:...:(man5/locale.5):32294: error: output above first line discarded grotty:...:(man5/locale.5):32294: error: output above first line discarded `\r` is a perfectly legal *roff escape sequence, but one generally never sees it in man pages. In that case, the input line in question was at the top of the "page" in continuous rendering mode, and so the attempt at a reverse vertical motion did indeed put the drawing position above the top of the page. grepping reveals no other occurrences of '\r' in the man-pages corpus. Signed-off-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-24proc_sys_user.5: tfixJakub Wilk1-1/+1
Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-24proc_pid_oom_score_adj.5: tfixJakub Wilk1-1/+1
Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-24proc_pid_mountinfo.5: spfixJakub Wilk1-1/+1
Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-24proc_crypto.5: spfixJakub Wilk1-1/+1
"Cypher" is a valid but less common spelling of "cipher". The latter is used everywhere else, so let's use it here too. Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-11-19man*/: srcfixG. Branden Robinson1-2/+6
Clean up in preparation for "MR sed". Format only one man page cross reference per input line. Begin parentheticals on their own input lines. Also, groff 1.23.0's (and Plan 9 from User Space's) `MR` is not a font style alternation macro; there is no "reversed" form as with `BR` and `RB`. So when a man page cross reference must be immediately preceded by punctuation, put that punctuation on the previous text line and use the `\c` escape sequence to connect them. Signed-off-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-10-31man*/: srcfix (Use .P instead of .PP or .LP)Alejandro Colomar36-387/+387
We're trying to "standardize" on a paragraphing macro from the three equivalent ones (P, PP, LP). We (somewhat arbitrarily) agreed on P. Scripted change: $ find man* -type f | xargs sed -i '/\.PP/s/PP/P/' $ find man* -type f | xargs sed -i '/\.LP/s/LP/P/' Suggested-by: "G. Branden Robinson" <branden@debian.org> Cc: Ingo Schwarze <schwarze@openbsd.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-10-23man*/: ffix (Use '.TQ' where appropriate)Alejandro Colomar2-16/+51
When there are multiple tags for a paragraph, using a single TP and separating the tags with commas makes the man(7) source more complex. It also has a disadvantage: when searching through a manual page, heuristics such as " --option" don't work so well. By using GNU's TQ, we simplify the source of the pages, and improve the ability to search them. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-09-30proc_sys.5, proc_sys_vm.5: Split /proc/sys/vm/ from proc_sys(5)Alejandro Colomar2-406/+420
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-09-30proc_sys.5, proc_sys_user.5: Split /proc/sys/user/ from proc_sys(5)Alejandro Colomar2-4/+18
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-09-30proc_sys.5, proc_sys_sunrpc.5: Split /proc/sys/proc/ from proc_sys(5)Alejandro Colomar2-5/+19
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-09-30proc_sys.5, proc_sys_proc.5: Split /proc/sys/proc/ from proc_sys(5)Alejandro Colomar2-3/+17
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-09-30proc_sys.5, proc_sys_net.5: Split /proc/sys/net/ from proc_sys(5)Alejandro Colomar2-20/+34
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-09-30proc_sys.5, proc_sys_kernel.5: Split /proc/sys/kernel/ from proc_sys(5)Alejandro Colomar2-677/+691
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-09-30proc_sys.5, proc_sys_fs.5: Split /proc/sys/fs/ from proc_sys(5)Alejandro Colomar2-457/+471
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-09-30proc_sys.5, proc_sys_dev.5: Split /proc/sys/dev/ from proc_sys(5)Alejandro Colomar2-6/+20
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-09-30proc_sys.5, proc_sys_debug.5: Split /proc/sys/debug/ from proc_sys(5)Alejandro Colomar2-3/+17
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-09-30proc_sys.5, proc_sys_abi.5: Split /proc/sys/abi/ from proc_sys(5)Alejandro Colomar2-10/+24
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-09-27tmpfs.5: Extend with new noswap documentationLuis Chamberlain1-0/+6
Linux commit 2c6efe9cf2d7 ("shmem: add support to ignore swap") merged as of v6.4 added support to disable swap for tmpfs mounts. This extends the man page to document that. Signed-off-by: Luis Chamberlain <mcgrof@kernel.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-09-07man5/: srcfix: '\" t commentAlejandro Colomar6-5/+1
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-09-03proc_self.5: Fix link pageAlejandro Colomar1-1/+1
Fixes: 68553d3f22ff ("proc.5, proc_pid.5, proc_self.5: Split /proc/PID/ (and /proc/self/) from proc(5)") Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5: Clean up after making sashimi of this pageAlejandro Colomar1-30/+3
- Remove outdated comments (they're on git, so it's not worth moving them to the appropriate pages). - Relicense with GPL-3.0-or-later, and add myself to copyleft. - Remove now-empty "Files and directories" subsection. - Remove now-irrelevant note about the page being a monster, which it is not anymore. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_zoneinfo.5: Split /proc/zoneinfo from proc(5)Alejandro Colomar2-5/+17
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_vmstat.5: Split /proc/vmstat from proc(5)Alejandro Colomar2-690/+702
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_version.5: Split /proc/version from proc(5)Alejandro Colomar2-15/+27
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_uptime.5: Split /proc/uptime from proc(5)Alejandro Colomar2-5/+17
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_tty.5: Split /proc/tty from proc(5)Alejandro Colomar2-4/+16
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_timer_stats.5: Split /proc/timer_stats from proc(5)Alejandro Colomar2-105/+117
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_timer_list.5: Split /proc/timer_list from proc(5)Alejandro Colomar2-6/+18
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_sysvipc.5: Split /proc/sysvipc/ from proc(5)Alejandro Colomar2-15/+25
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_sysrq-trigger.5: Split /proc/sysrq-trigger from proc(5)Alejandro Colomar2-13/+25
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_sys.5: Split /proc/sys/ from proc(5)Alejandro Colomar2-1610/+1623
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_swaps.5: Split /proc/swaps from proc(5)Alejandro Colomar2-5/+17
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_stat.5: Split /proc/stat from proc(5)Alejandro Colomar2-128/+140
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_slabinfo.5: Split /proc/slabinfo from proc(5)Alejandro Colomar2-6/+18
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_scsi.5: Split /proc/scsi/ from proc(5)Alejandro Colomar2-54/+66
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_profile.5: Split /proc/profile from proc(5)Alejandro Colomar2-12/+24
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pci.5: Split /proc/pci from proc(5)Alejandro Colomar2-16/+28
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_partitions.5: Split /proc/partitions from proc(5)Alejandro Colomar2-4/+16
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_mtrr.5: Split /proc/mtrr from proc(5)Alejandro Colomar2-12/+24
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_modules.5: Split /proc/modules from proc(5)Alejandro Colomar2-5/+17
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_meminfo.5: Split /proc/meminfo from proc(5)Alejandro Colomar2-315/+327
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_malloc.5: Split /proc/malloc from proc(5)Alejandro Colomar2-6/+18
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_locks.5: Split /proc/locks from proc(5)Alejandro Colomar2-106/+118
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_loadavg.5: Split /proc/loadavg from proc(5)Alejandro Colomar2-15/+27
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_kpageflags.5: Split /proc/kpageflags from proc(5)Alejandro Colomar2-62/+75
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_kpagecount.5: Split /proc/kpagecount from proc(5)Alejandro Colomar2-12/+24
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_kpagecgroup.5: Split /proc/kpagecgroup from proc(5)Alejandro Colomar2-13/+25
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_kmsg.5: Split /proc/kmsg from proc(5)Alejandro Colomar2-16/+28
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_keys.5, proc_key-users.5: Split /proc/keys (and ↵Alejandro Colomar3-8/+21
/proc/key-users) from proc(5) Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_kcore.5: Split /proc/kcore from proc(5)Alejandro Colomar2-12/+24
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_kallsyms.5, proc_ksyms.5: Split /proc/kallsyms (and ↵Alejandro Colomar3-12/+26
/proc/ksyms) from proc(5) Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_ioports.5: Split /proc/ioports from proc(5)Alejandro Colomar2-4/+16
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_iomem.5: Split /proc/iomem from proc(5)Alejandro Colomar2-3/+15
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_interrupts.5: Split /proc/interrupts from proc(5)Alejandro Colomar2-10/+22
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_ide.5: Split /proc/ide/ from proc(5)Alejandro Colomar2-25/+37
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_fs.5: Split /proc/fs/ from proc(5)Alejandro Colomar2-6/+18
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_filesystems.5: Split /proc/filesystems from proc(5)Alejandro Colomar2-21/+33
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_fb.5: Split /proc/fb from proc(5)Alejandro Colomar2-5/+17
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_execdomains.5: Split /proc/execdomains from proc(5)Alejandro Colomar2-4/+16
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_driver.5: Split /proc/driver/ from proc(5)Alejandro Colomar2-3/+15
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_dma.5: Split /proc/dma from proc(5)Alejandro Colomar2-4/+16
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_diskstats.5: Split /proc/diskstats from proc(5)Alejandro Colomar2-9/+21
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_devices.5: Split /proc/devices from proc(5)Alejandro Colomar2-4/+16
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_cpuinfo.5: Split /proc/cpuinfo from proc(5)Alejandro Colomar2-12/+24
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_crypto.5: Split /proc/crypto from proc(5)Alejandro Colomar2-14/+26
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_config.gz.5: Split /proc/config.gz from proc(5)Alejandro Colomar2-28/+40
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_cmdline.5: Split /proc/cmdline from proc(5)Alejandro Colomar2-10/+22
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_cgroups.5: Split /proc/cgroups from proc(5)Alejandro Colomar2-4/+16
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_bus.5: Split /proc/bus/ from proc(5)Alejandro Colomar2-23/+35
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_buddyinfo.5: Split /proc/buddyinfo from proc(5)Alejandro Colomar2-46/+58
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_apm.5: Split /proc/apm from proc(5)Alejandro Colomar2-5/+17
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_tid_children.5: Split /proc/TID/children from proc(5)Alejandro Colomar2-25/+37
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_task.5, proc_tid.5, proc_thread-self.5: Split ↵Alejandro Colomar4-85/+99
/proc/PID/task/ (and /proc/TID/, /proc/thread-self/) from proc(5) Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid.5, proc_self.5: Split /proc/PID/ (and /proc/self/) from proc(5)Alejandro Colomar3-61/+74
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_wchan.5: Split /proc/PID/wchan from proc(5)Alejandro Colomar2-9/+21
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_timerslack_ns.5: Split /proc/PID/timerslack_ns from proc(5)Alejandro Colomar2-29/+41
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_timers.5: Split /proc/PID/timers from proc(5)Alejandro Colomar2-70/+83
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_syscall.5: Split /proc/PID/syscall from proc(5)Alejandro Colomar2-21/+33
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_status.5: Split /proc/PID/status from proc(5)Alejandro Colomar2-354/+366
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_statm.5: Split /proc/PID/statm from proc(5)Alejandro Colomar2-33/+46
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_stat.5: Split /proc/PID/stat from proc(5)Alejandro Colomar2-367/+380
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_stack.5: Split /proc/PID/stack from proc(5)Alejandro Colomar2-13/+25
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_smaps.5: Split /proc/PID/smaps from proc(5); XXX: what's s ↵Alejandro Colomar2-116/+128
in smaps? Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_setgroups.5: Split /proc/PID/setgroups from proc(5)Alejandro Colomar2-4/+16
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_seccomp.5: Split /proc/PID/seccomp from proc(5)Alejandro Colomar2-24/+36
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_projid_map.5: Split /proc/PID/projid_map from proc(5)Alejandro Colomar2-5/+17
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_root.5: Split /proc/PID/root/ from proc(5)Alejandro Colomar2-63/+75
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_personality.5: Split /proc/PID/personality from proc(5)Alejandro Colomar2-11/+23
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_pagemap.5: Split /proc/PID/pagemap from proc(5)Alejandro Colomar2-65/+77
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_oom_score.5: Split /proc/PID/oom_score from proc(5)Alejandro Colomar2-45/+58
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_oom_score_adj.5, proc_pid_oom_adj.5: Split ↵Alejandro Colomar3-103/+118
/proc/PID/oom_score_adj (and /proc/PID/oom_adj) from proc(5) Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_numa_maps.5: Split /proc/PID/numa_maps from proc(5)Alejandro Colomar2-4/+16
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_ns.5: Split /proc/PID/ns/ from proc(5)Alejandro Colomar2-8/+20
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_net.5, proc_net.5: Split /proc/PID/net/ (and /proc/net/) ↵Alejandro Colomar3-286/+299
from proc(5) Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_mountstats.5: Split /proc/PID/mountstats from proc(5)Alejandro Colomar2-34/+46
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_mounts.5, proc_mounts.5: Split /proc/PID/mounts (and ↵Alejandro Colomar3-37/+50
/proc/mounts) from proc(5) Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_mountinfo.5: Split /proc/PID/mountinfo from proc(5)Alejandro Colomar2-112/+124
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_mem.5: Split /proc/PID/mem from proc(5)Alejandro Colomar2-12/+24
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_maps.5: Split /proc/PID/maps from proc(5)Alejandro Colomar2-144/+157
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_map_files.5: Split /proc/PID/map_files/ from proc(5)Alejandro Colomar2-60/+72
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_limits.5: Split /proc/PID/limits from proc(5)Alejandro Colomar2-13/+25
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_io.5: Split /proc/PID/io from proc(5)Alejandro Colomar2-86/+98
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_uid_map.5, proc_pid_gid_map.5: Split /proc/PID/[ug]id_map ↵Alejandro Colomar3-8/+21
from proc(5) Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_fdinfo.5: Split /proc/PID/fdinfo/ from proc(5)Alejandro Colomar2-288/+300
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_fd.5: Split /proc/PID/fd/ from proc(5)Alejandro Colomar2-149/+161
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_exe.5: Split /proc/PID/exe from proc(5)Alejandro Colomar2-47/+59
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_environ.5: Split /proc/PID/environ from proc(5)Alejandro Colomar2-36/+48
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_cwd.5: Split /proc/PID/cwd from proc(5)Alejandro Colomar2-24/+36
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_cpuset.5: Split /proc/PID/cpuset from proc(5)Alejandro Colomar2-5/+17
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_coredump_filter.5: Split /proc/PID/coredump_filter from proc(5)Alejandro Colomar2-4/+16
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_comm.5: Split /proc/PID/comm from proc(5)Alejandro Colomar2-37/+49
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_cmdline.5: Split /proc/PID/cmdline from proc(5)Alejandro Colomar2-37/+49
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_clear_refs.5: Split /proc/PID/clear_refs from proc(5)Alejandro Colomar2-75/+88
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_cgroup.5: Split /proc/PID/cgroup from proc(5)Alejandro Colomar2-4/+16
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_auxv.5: Split /proc/PID/auxv from proc(5)Alejandro Colomar2-15/+27
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_autogroup.5: Split /proc/PID/autogroup from proc(5)Alejandro Colomar2-5/+17
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-15proc.5, proc_pid_attr.5: Split /proc/PID/attr/ from proc(5)Alejandro Colomar2-125/+137
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-14proc.5: srcfixAlejandro Colomar1-2/+2
Slightly reformat copyright lines. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-14proc.5: /proc/PID/status: Add Seccomp_filters entrySascha Grunert1-0/+7
The field exists since Linux 5.9, in commit c818c03b661c ("seccomp: Report number of loaded filters in /proc/$pid/status"). Cc: Kees Cook <keescook@chromium.org> Cc: Stefan Puiu <stefan.puiu@gmail.com> Signed-off-by: Sascha Grunert <saschagrunert@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-08-12tmpfs.5: Document that size/blocks=0 and nr_inodes=0 remove the limitsнаб1-0/+4
Bitten by this again. Behaviour blames back to at least 2005 (probably original to shmem.c), documented upstream in Documentation/filesystems/tmpfs.rst (formerly .txt). For example: # mount -t tmpfs -o size=0 tmpfs /etc/ # df /etc/ Filesystem 1k-blocks Used Avail Use% Mounted on tmpfs 0 0 0 - /etc # head -c100M < /dev/urandom > /etc/passwd # df /etc/ Filesystem 1k-blocks Used Avail Use% Mounted on tmpfs 0 0 0 - /etc # ls -l /etc/passwd -rw-r--r-- 1 0 0 104857600 08-12 19:55 /etc/passwd # du /etc/passwd 204800 /etc/passwd whereas the current manual insinuates head should ENOSPC instantly. Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Cc: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-07-28tmpfs.5: Update reference to CONFIG_TRANSPARENT_HUGEPAGEJohn Hubbard1-1/+1
In commit 462a385e9a2 ("tmpfs.5: Document current mount options"), there is a reference to CONFIG_TRANSPARENT_HUGE_PAGECACHE. However, that option was removed from the kernel via commit 396bcc5299c2 ("mm: remove CONFIG_TRANSPARENT_HUGE_PAGECACHE"), a couple of years later. The net effect is that CONFIG_TRANSPARENT_HUGEPAGE is now used in all the remaining places in the kernel where CONFIG_TRANSPARENT_HUGE_PAGECACHE had previously been used. This has caused some minor confusion at the man page level, though. So let's fix it by updating the man page to refer to CONFIG_TRANSPARENT_HUGEPAGE. Reported-by: Vahid Noormofidi <vnoormof@nvidia.com> Cc: Matthew Wilcox (Oracle) <willy@infradead.org> Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com> Cc: Andrew Morton <akpm@linux-foundation.org> Cc: Carsten Grohmann <carstengrohmann@gmx.de> Cc: Mike Frysinger <vapier@gentoo.org> Signed-off-by: John Hubbard <jhubbard@nvidia.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-07-15dir_colors.5: Relicense pageAlejandro Colomar1-9/+2
On 2023-07-08 22:14, Martin (Joey) Schulze wrote: > For the record, > > I would like to re-license dir_colors(5) under the GPLv2+ > > Please adjust the manpage source accordingly. > > .\" Copyright (c) 2001 Martin Schulze <joey@infodrom.org> > .\" > .\" This is free documentation; you can redistribute it and/or > .\" modify it under the terms of the GNU General Public License as > .\" published by the Free Software Foundation; either version 2 of > .\" the License, or (at your option) any later version. > .\" > .\" The GNU General Public License's references to "object code" > .\" and "executables" are to be interpreted as the output of any > .\" document formatting or typesetting system, including > .\" intermediate and printed output. > .\" > .\" This manual is distributed in the hope that it will be useful, > .\" but WITHOUT ANY WARRANTY; without even the implied warranty of > .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the > .\" GNU General Public License for more details. > .\" > .\" You should have received a copy of the GNU General Public > .\" License along with this manual; if not, write to the Free > .\" Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, > .\" USA. > > This should help keep the manpage free and a version in Fedora. Link: <https://gitlab.com/fedora/legal/fedora-license-data/-/issues/211> Reported-by: Adam Dobes <adobes@redhat.com> Cc: Brian Inglis <Brian.Inglis@Shaw.ca> Cc: Martin (Joey) Schulze <joey@infodrom.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-07-08proc.5: Clarify that boot arguments can be embedded in imagePaul E. McKenney1-0/+3
With the advent of the CONFIG_BOOT_CONFIG Kconfig option, kernel boot arguments can now be embedded in the kernel image, either attached to the end of initramfs or embedded in the kernel itself. Document this possibility in the /proc/cmdline entry of proc.5. Signed-off-by: Paul E. McKenney <paulmck@kernel.org> Cc: Michael Kerrisk <mtk.manpages@gmail.com> Cc: Jonathan Corbet <corbet@lwn.net> Cc: Andrew Morton <akpm@linux-foundation.org> Cc: Nick Desaulniers <ndesaulniers@google.com> Cc: Vlastimil Babka <vbabka@suse.cz> Cc: Johannes Weiner <hannes@cmpxchg.org> Reviewed-by: Masami Hiramatsu <mhiramat@kernel.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-05-25proc.5: Clarify the format of /proc/$PID/cmdlineGünther Noack1-2/+13
It is possible to produce /proc/$PID/cmdline files which do not follow the NUL-seperated format, by using the tricks described in the paragraph below. Signed-off-by: Günther Noack <gnoack@google.com> [ fix semantic newlines ] Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-05-05resolv.conf.5: tfixJakub Wilk1-1/+1
Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-05-03man*/, man.ignore.grep: srcfix; warn about blank linesAlejandro Colomar6-31/+31
- Use the dummy character to avoid warnings in examples. - Re-enable the warning. Suggested-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-29man*/: srcfixAlejandro Colomar1-3/+1
Reported-by: groff(1) (`make build-catman-troff`) Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-17proc.5: tfixGuillem Jover1-1/+1
Use Ctrl-Alt-Del instead of ctrl-alt-del, as used in all other instances. Signed-off-by: Guillem Jover <guillem@hadrons.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-17proc.5: Document that /proc/PID/oom_adj is no longer presentGuillem Jover1-1/+2
See kernel commit 01dc52ebdf472f77cca623ca693ca24cfc0f1bbe. Signed-off-by: Guillem Jover <guillem@hadrons.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-17proc.5: A process can increase its own /proc/PID/oom_adj settingGuillem Jover1-1/+4
See kernel commit 8fb4fc68ca391862b061b3d358a288ccf6abed39. Signed-off-by: Guillem Jover <guillem@hadrons.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-17proc.5: Document exact /proc/PID/exe behavior on unlinked pathnamesGuillem Jover1-1/+1
Add the space which gets appended before the "(deleted)" marker. Signed-off-by: Guillem Jover <guillem@hadrons.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-14resolv.conf.5: Add option no-aaaaLukas Javorsky1-0/+23
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-10erofs.5: Minor tweaks to наб's patchAlejandro Colomar1-5/+9
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-10filesystems.5, erofs.5: add erofs documentationнаб2-1/+102
Modelled after tmpfs(5) ‒ there's a listing of mount options, and a summary of limitations. The feature flags are described in mkfs.erofs, and they're versioned and maintained upstream quite well there, so no need to duplicate those, since you only care on image creation. The real value add is the mount options, but I cannot figure out how device_id and fsid interact with the system at large, so I just noted they're there. State as of Linux 6.3-rc5. Also, remove explicit .TP indent in filesystems.5 since we're already touching this hunk: all entries sans iso9660 and Reiserfs fall within the default prevailing indent, so no need to specify a wide one. Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-08proc.5: note effective removal of /proc/execdomains in v4.1наб1-1/+2
The file was turned into a fixed string in upstream commit 973f911f55a0e510dd6db8bbb29cd82ff138d3c0 ("Remove execution domain support"); the entire mechanism was fully removed in a patchset by Weinberger ending at commit 720d70716d137c0cb83b9a5279c384286c02a1c0 ("sparc: Fix execution domain removal"). Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-03man*/: ffixAlejandro Colomar1-1/+2
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-02proc.5: NAME: Add "system information, and sysctl"наб1-1/+1
procfs hosts a whole host of information about the system, as well as sysctls; proc(5) hosts a description of a lot of sysctls, and at present there's no way to find that out. Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Cc: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-04-01proc.5: Fix caps needed to read map_files contentsYounes Manton1-1/+1
imachug@yandex.ru testing CRIU noticed that the documentation for proc's map_files directory with respect to CAP_CHECKPOINT_RESTORE and namespaces appears to be wrong. The text reads: > since Linux 5.9, the reading process must have > either CAP_SYS_ADMIN or CAP_CHECKPOINT_RESTORE in the user > namespace where it resides. The reporter noted that the user actually needs the capabilities in the initial user namespace, not in the namespace the process resides in. As far as I can tell this appears to be the case. The text was introduced in 167f94b707148bcd46fe39c7d4ebfada9eed88f6 and refers to kernel commit 12886f8ab10ce6a09af1d92535d49c81aaa215a8. The code and message in the kernel commit refer to the initial user namespace. An example program and shell session verifying the existing behaviour follows: $ uname -r 5.15.0-52-generic $ ./test.sh + make rmf cc rmf.c -o rmf + sudo setcap cap_checkpoint_restore-eip ./rmf + ./rmf 19582: = Can't read map_files/ entry: Operation not permitted + sudo setcap cap_checkpoint_restore+eip ./rmf + ./rmf 19588: cap_checkpoint_restore=ep + unshare --user ./rmf 19591: cap_checkpoint_restore=ep Can't read map_files/ entry: Operation not permitted $ cat rmf.c int main(int argc, char **argv) { DIR *mfd; struct dirent *mfe; struct stat mfstat; int ret; system("getpcaps $PPID"); chdir("/proc/self/map_files"); mfd = opendir("."); do { mfe = readdir(mfd); } while (!strcmp(mfe->d_name, ".") || !strcmp(mfe->d_name, "..")); if (ret = stat(mfe->d_name, &mfstat)) perror("Can't read map_files/ entry"); closedir(mfd); return ret; } Signed-off-by: Younes Manton <younes.m@gmail.com> Cc: <imachug@yandex.ru> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-31proc.5: Document KPF_PGTABLE for /proc/kpageflagsMarco Bonelli1-0/+2
KPG_PGTABLE (bit 26) was introduced in Linux v4.18 (commit 1d40a5ea01d53251c23c7be541d3f4a656cfc537). Signed-off-by: Marco Bonelli <marco@mebeim.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-30man*/, man-pages.7: VERSIONS, STANDARDS, HISTORY: Reorganize sectionsAlejandro Colomar3-14/+13
- Add a new HISTORY section that covers the history of an API, both regarding implementations and regarding old standards. This was previously covered in VERSIONS, and in some cases in STANDARDS. - Repurpose VERSIONS to cover differing implementations in _current_ systems. - STANDARDS is reduced to only cover current versions of standards. That basically means only C11 (C99 has been superseeded by C11; C17 is just a bugfix of C11, so not really a new version), and POSIX.1-2008 (*-2001 was superseeded by *-2008; *-2017 was just a bugfix for *-2008). The section also mentions for example 'Linux', 'GNU' or 'BSD' when a non-standard API is Linux- or GNU-only or if it's (de-facto) standard in the BSDs. - In some cases content that should go into one of these sections was in NOTES. Move it from there to where it corresponds. - In the SYNOPSIS, I added [[deprecated]] in some functions that I found are deprecated by the relevant standards. - A few other related changes... Cc: Oskari Pirhonen <xxc3ncoredxx@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-09tzfile.5, tzselect.8, zdump.8, zic.8: sync pages from tzdbAlejandro Colomar1-4/+1
Cc: Paul Eggert <eggert@cs.ucla.edu> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-08tzfile.5, tzselect.8: sync from tzdb upstreamPaul Eggert1-61/+133
This makes tzfile.5 and tzselect.8 a copy of the tzdb develoment version (commit 12b48faf10c265ee3ea1aad8cdb5c8239eea65a0), except that man-pages boilerplate surrounds the copyright notice, and the .TH line uses man-pages format. Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-03-08man*/: ffix (semantic newlines; commas)Alejandro Colomar2-7/+12
Reported-by: mandoc(1) (make lint-man-mandoc) Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-10man*/: srcfix (^ -> \[ha])G. Branden Robinson1-2/+2
Use correct *roff special character for hat/caret/circumflex accent. Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05Many pages: Use \[bu] instead of \(buAlejandro Colomar8-76/+76
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05Various pages: Use \[rq] instead of \(rqAlejandro Colomar1-2/+2
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05Various pages: Use \[lq] instead of \(lqAlejandro Colomar1-2/+2
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05Many pages: Use \[ha] instead of \(haAlejandro Colomar3-9/+9
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05Many pages: Use \[ti] instead of \(tiAlejandro Colomar5-6/+6
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05Many pages: Use \[em] instead of \(emAlejandro Colomar2-5/+5
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05Many pages: Use \[en] instead of \(enAlejandro Colomar1-6/+6
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05Many pages: Use \[dq] instead of \(dqAlejandro Colomar2-4/+4
This improves readability in the source code, since it delimits where the escape sequence ends. Cc: наб <nabijaczleweli@nabijaczleweli.xyz> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Cc: Brian Inglis <Brian.Inglis@Shaw.ca> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-05Many pages: Use \[aq] instead of \(aqAlejandro Colomar14-50/+50
This improves readability in the source code, since it delimits where the escape sequence ends. Cc: наб <nabijaczleweli@nabijaczleweli.xyz> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Cc: Brian Inglis <Brian.Inglis@Shaw.ca> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-01-22ttytype.5: ffixAlejandro Colomar1-1/+2
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-01-11prctl.2, proc.5: Document VMA namingNick Gregory1-0/+14
Bring in man page changes from the patch set by Colin Cross, and document the corresponding virtual names in procfs. Link: <https://lore.kernel.org/linux-mm/20211019215511.3771969-2-surenb@google.com/> Signed-off-by: Nick Gregory <nick@nickgregory.me> Reviewed-by: Suren Baghdasaryan <surenb@google.com> Cc: Colin Cross <ccross@google.com> Cc: Kees Cook <keescook@chromium.org> Cc: Pasha Tatashin <tatashin@google.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-01-07Many pages: TH: Use lowercaseAlejandro Colomar3-3/+3
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-16utmp.5: STANDARDS: Specify that it's an XSI extensionAlejandro Colomar1-1/+2
Cc: Serge Hallyn <serge@hallyn.com> Cc: Iker Pedrosa <ipedrosa@redhat.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-15Many pages: Add '\" t' comment where necessaryAlejandro Colomar2-0/+2
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-12core.5: Clarify that RLIMIT_CORE is ignored when piping.Alejandro Colomar1-0/+3
Reported-by: Luca Versari <veluca93@gmail.com> Closes: <https://bugzilla.kernel.org/show_bug.cgi?id=216648> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-05filesystems.5: Don't refer to dead software; use a more generic termAlejandro Colomar1-1/+1
Reported-by: Helge Kreutzmann <debian@helgefjell.de> Reported-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-12-04ttytype.5: 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-04proc.5: 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 Colomar9-74/+74
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-04passwd.5: ffixAlejandro Colomar1-2/+6
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-04filesystems.5: wfixAlejandro Colomar1-1/+1
ext2 is not a high performance fs by today's standards. And it's not used in Linux by default. 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 Colomar2-3/+9
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-05nsswitch.conf.5: Current glibc reloads this configuration fileFlorian Weimer1-5/+7
The implementation happened across multiple glibc commits, but the work was completed for glibc 2.33. Signed-off-by: Florian Weimer <fweimer@redhat.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-10-30Many pages: Use correct letter case in page titles (TH)Alejandro Colomar33-33/+33
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-29Many pages: Use a consistent style for listsAlejandro Colomar8-95/+94
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 Colomar2-34/+68
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-09dist.mk, All pages: .TH: Generate date at 'make dist'Alejandro Colomar36-36/+36
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-09getent.1, iconv.1, intro.1, ldd.1, locale.1, localedef.1, memusage.1, ↵Alejandro Colomar37-37/+37
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-08proc.5: tfixAndrea Cervesato1-2/+0
"KernelPageSize" and "MMUPageSize" are repeated in the /proc/[pid]/smaps format example. Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com> Fixes: 6861f8f0c7 "proc.5: Improve description of the KernelPageSize and [...]" Signed-off-by: Alejandro Colomar <alx@kernel.org>
2022-09-15Various pages: EXAMPLES: Use unsigned types for loop iteratorsAlex Colomar1-2/+2
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-09Revert "src.mk, All pages: Move man* to man/"Alejandro Colomar42-0/+16811
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 Colomar42-16811/+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-01hosts.5: Use "example.org" as example domainJakub Wilk1-3/+3
Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
2022-08-21All pages: Remove the 5th argument to .THAlejandro Colomar36-36/+36
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 Colomar36-36/+36
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-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-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>
generated by cgit 1.2.3-korg (git 2.43.0) at 2025-11-30 02:31:43 +0000