Skip to contentSkip to conversation

man/man2/*: Update history of syscalls H-M

PATCH In review Seth McDonald 4 participants 32 messages Jan 26 – Feb 17 Man-pages: manual pages for Linux -- Sections 2, 3, 4, 5, and 7

lore
Share & tools
lore
#0 lore raw

cover man/man2/*: Update history of syscalls H-M

Hi all,

This set updates the history of system calls H to M.

While I have been thorough with my research, I would encourage those interested to double-check that my edits make sense given the listed sources. Particularly for linkat(2), SEEK_DATA/SEEK_HOLE, mkdirat(2), and mincore(2), since they took significantly more time and research than other functions.

Seth McDonald (21):
man/man2/ioctl_eventpoll.2: HISTORY: ffix man/man2/kill.2: HISTORY: Update POSIX appearances of kill(2) man/man2/link.2: HISTORY: Change order of linkat(2) man/man2/link.2: HISTORY: Update POSIX appearances of link(2) man/man2/listen.2: HISTORY: Change order man/man2/lseek.2: HISTORY: Update appearances of SEEK_{DATA,HOLE} man/man2/lseek.2: HISTORY: Update POSIX appearances of lseek(2) man/man2/mincore.2: HISTORY: Update appearances of mincore(2) man/man2/mkdir.2: HISTORY: Change order of mkdirat(2) man/man2/mkdir.2: HISTORY: Update BSD and POSIX appearances of

    mkdir(2)
  man/man2/mknod.2: HISTORY: Change order of mknodat(2)
  man/man2/mknod.2: HISTORY: Update POSIX appearances of mknod(2)
  man/man2/mknod.2: STANDARDS: Update
  man/man2/mlock.2: HISTORY: Update POSIX appearances of
    m(un)lock(all)(2)
  man/man2/mmap.2: HISTORY: Update POSIX appearances of m(un)map(2)
  man/man2/{mount_setattr,move_mount}.2: HISTORY: ffix
  man/man2/mprotect.2: HISTORY: Update POSIX appearances of mprotect(2)
  man/man2/msgctl.2: STANDARDS, HISTORY: Update POSIX appearances of
    msgctl(2)
  man/man2/msgget.2: STANDARDS, HISTORY: Update POSIX appearances of
    msgget(2)
  man/man2/msgop.2: STANDARDS, HISTORY: Update POSIX appearances of
    msg{rcv,snd}(2)

man/man2/msync.2: HISTORY: Update POSIX appearances of msync(2)

 man/man2/ioctl_eventpoll.2 |  2 +-
 man/man2/kill.2            |  4 +++-
 man/man2/link.2            | 10 ++++++----
 man/man2/listen.2          |  4 ++--
 man/man2/lseek.2           | 10 +++++++---
 man/man2/mincore.2         | 13 ++++++++-----
 man/man2/mkdir.2           |  8 +++++---
 man/man2/mknod.2           | 11 +++++++----
 man/man2/mlock.2           |  3 ++-
 man/man2/mmap.2            |  5 ++++-
 man/man2/mount_setattr.2   |  2 +-
 man/man2/move_mount.2      |  2 +-
 man/man2/mprotect.2        |  4 +++-
 man/man2/msgctl.2          |  6 ++++--
 man/man2/msgget.2          |  6 ++++--
 man/man2/msgop.2           |  6 ++++--
 man/man2/msync.2           |  3 ++-
 17 files changed, 64 insertions(+), 35 deletions(-)

Range-diff against v0:

 -:  ------------ >  1:  d109f3dc06e2 man/man2/ioctl_eventpoll.2: HISTORY: ffix
 -:  ------------ >  2:  55de16b213bf man/man2/kill.2: HISTORY: Update POSIX appearances of kill(2)
 -:  ------------ >  3:  17eacf0f2d3e man/man2/link.2: HISTORY: Change order of linkat(2)
 -:  ------------ >  4:  bec317b8ee88 man/man2/link.2: HISTORY: Update POSIX appearances of link(2)
 -:  ------------ >  5:  2024c82a058d man/man2/listen.2: HISTORY: Change order
 -:  ------------ >  6:  bcf9f5113f3c man/man2/lseek.2: HISTORY: Update appearances of SEEK_{DATA,HOLE}
 -:  ------------ >  7:  2dd12d136bf0 man/man2/lseek.2: HISTORY: Update POSIX appearances of lseek(2)
 -:  ------------ >  8:  817af323707e man/man2/mincore.2: HISTORY: Update appearances of mincore(2)
 -:  ------------ >  9:  8b25a256e60f man/man2/mkdir.2: HISTORY: Change order of mkdirat(2)
 -:  ------------ > 10:  347e36c11666 man/man2/mkdir.2: HISTORY: Update BSD and POSIX appearances of mkdir(2)
 -:  ------------ > 11:  d3da8260e1bc man/man2/mknod.2: HISTORY: Change order of mknodat(2)
 -:  ------------ > 12:  b0feda20f21d man/man2/mknod.2: HISTORY: Update POSIX appearances of mknod(2)
 -:  ------------ > 13:  32bd25fd3630 man/man2/mknod.2: STANDARDS: Update
 -:  ------------ > 14:  67bf0c1aa133 man/man2/mlock.2: HISTORY: Update POSIX appearances of m(un)lock(all)(2)
 -:  ------------ > 15:  57292b4f60c4 man/man2/mmap.2: HISTORY: Update POSIX appearances of m(un)map(2)
 -:  ------------ > 16:  b8f4e6fa54e7 man/man2/{mount_setattr,move_mount}.2: HISTORY: ffix
 -:  ------------ > 17:  4e1acc0f5e00 man/man2/mprotect.2: HISTORY: Update POSIX appearances of mprotect(2)
 -:  ------------ > 18:  024ce32c9da5 man/man2/msgctl.2: STANDARDS, HISTORY: Update POSIX appearances of msgctl(2)
 -:  ------------ > 19:  975e61bea29f man/man2/msgget.2: STANDARDS, HISTORY: Update POSIX appearances of msgget(2)
 -:  ------------ > 20:  86e7c24b1428 man/man2/msgop.2: STANDARDS, HISTORY: Update POSIX appearances of msg{rcv,snd}(2)
 -:  ------------ > 21:  d106bca86ec1 man/man2/msync.2: HISTORY: Update POSIX appearances of msync(2)

base-commit: 6754bd1a126ed1e9b7d9c2bc1d221681f5182bb3

Signature · 1 line
2.47.3
#1 lore raw

PATCH 1/21 man/man2/ioctl_eventpoll.2: HISTORY: ffix

Commas are more consistent with other man pages.

---
 man/man2/ioctl_eventpoll.2 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
man/man2/ioctl_eventpoll.2 +1 -1
index 2b36458e5358..9e7748f4e9ba 100644
@@ -124,7 +124,7 @@ .SH STANDARDS
 .SH HISTORY
 .\" linux.git commit 18e2bf0edf4dd88d9656ec92395aa47392e85b61
 .\" glibc.git commit 92c270d32caf3f8d5a02b8e46c7ec5d9d0315158
-Linux 6.9.
+Linux 6.9,
 glibc 2.40.
 .SH EXAMPLES
 .EX
Signature · 1 line
2.47.3
#2 lore raw

PATCH 2/21 man/man2/kill.2: HISTORY: Update POSIX appearances of kill(2)

In reply to Seth McDonald

kill(2) appeared in POSIX.1-1988.[1]

[1] IEEE Std 1003.1-1988, Section 3.3.2 "Send a Signal to a Process".

---
 man/man2/kill.2 | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
man/man2/kill.2 +3 -1
index 7ec979c07646..13222f135a06 100644
@@ -118,7 +118,9 @@ .SH ERRORS
 .SH STANDARDS
 POSIX.1-2024.
 .SH HISTORY
-POSIX.1-2001, SVr4, 4.3BSD.
+4.3BSD,
+SVr4,
+POSIX.1-1988.
 .SS Linux notes
 Across different kernel versions, Linux has enforced different rules
 for the permissions required for an unprivileged process
Signature · 1 line
2.47.3
#3 lore raw

PATCH 3/21 man/man2/link.2: HISTORY: Change order of linkat(2)

In reply to Seth McDonald

glibc 2.4 released on 2006-03-06.[1] Linux 2.6.16 released on 2006-03-20.[2] So chronologically list glibc before Linux.

POSIX.1-2008 released in 2008 (shocker!). However, glibc's addition of linkat(2) on 2005-12-16 declared the function in posix/unistd.h,[3] implying it was known (or at least suspected) to have been proposed for inclusion in POSIX.1-2008.[4] So chronologically list POSIX before glibc.

[1] McGrath, Roland (6 Mar 2006). "GNU C Library version 2.4 release". info-gnu (Mailing list).
<https://lists.gnu.org/archive/html/info-gnu/2006-03/msg00000.html>
[2] Linux Kernel Distribution System (20 Mar 2006). "Linux kernel 2.6.16 released". linux-kernel-announce (Mailing list).
<https://lore.kernel.org/linux-kernel-announce/[email protected]>
[3] Drepper, Ulrich (16 Dec 2005). "* sysdeps/unix/sysv/linux/renameat.c: Move errno setting code in". GNU C Library master sources (Git repository).
<https://sourceware.org/git/?p=glibc.git;a=commit;h=5c46041a9c8e0431f0b329a94becfc5d576d12cb>
[4] IEEE Std 1003.1-2008, Volume 2, Chapter 3 "System Interfaces", pp. 1216-1220.
<https://pubs.opengroup.org/onlinepubs/9699919799.2008edition/functions/link.html>

---
 man/man2/link.2 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
man/man2/link.2 +3 -3
index 964f564d7043..dd8bc1bc2826 100644
@@ -392,9 +392,9 @@ .SH HISTORY
 .\" X/OPEN does not document EFAULT, ENOMEM or EIO.
 .TP
 .BR linkat ()
-POSIX.1-2008.
-Linux 2.6.16,
-glibc 2.4.
+POSIX.1-2008,
+glibc 2.4,
+Linux 2.6.16.
 .SH NOTES
 Hard links, as created by
 .BR link (),
Signature · 1 line
2.47.3
#4 lore raw

PATCH 4/21 man/man2/link.2: HISTORY: Update POSIX appearances of link(2)

In reply to Seth McDonald

link(2) appeared in POSIX.1-1988.[1]

[1] IEEE Std 1003.1-1988, Section 5.3.4 "Link to a File".

---
 man/man2/link.2 | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
man/man2/link.2 +3 -1
index dd8bc1bc2826..603c6f9011d1 100644
@@ -386,7 +386,9 @@ .SH STANDARDS
 .SH HISTORY
 .TP
 .BR link ()
-SVr4, 4.3BSD, POSIX.1-2001 (but see VERSIONS).
+4.3BSD,
+SVr4,
+POSIX.1-1988 (but see VERSIONS).
 .\" SVr4 documents additional ENOLINK and
 .\" EMULTIHOP error conditions; POSIX.1 does not document ELOOP.
 .\" X/OPEN does not document EFAULT, ENOMEM or EIO.
Signature · 1 line
2.47.3
#5 lore raw

PATCH 5/21 man/man2/listen.2: HISTORY: Change order

In reply to Seth McDonald

4.2BSD released way before POSIX.1-2001, so chronologically list BSD before POSIX.

---
 man/man2/listen.2 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
man/man2/listen.2 +2 -2
index 0af616689ce1..65ad45de7645 100644
@@ -81,8 +81,8 @@ .SH ERRORS
 .SH STANDARDS
 POSIX.1-2024.
 .SH HISTORY
-POSIX.1-2001, 4.4BSD
-(first appeared in 4.2BSD).
+4.2BSD,
+POSIX.1-2001.
 .SH NOTES
 To accept connections, the following steps are performed:
 .RS 4
Signature · 1 line
2.47.3
#6 lore raw

PATCH 6/21 man/man2/lseek.2: HISTORY: Update appearances of SEEK_{DATA,HOLE}

In reply to Seth McDonald

SEEK_DATA and SEEK_HOLE appeared in Solaris no later than 2005-12-12, when a ZFS developer stated in a blog post that "[a]t this [time of] writing, SEEK_HOLE and SEEK_DATA are Solaris-specific."[1] The release notes for Solaris 10 are dated to 2005-12.[2] So the constants were likely added in Solaris 10.

They were added to FreeBSD on 2007-04-05,[3] before being released in FreeBSD 7.0 - the release notes stating that "[s]upport for Sun's ZFS has been added" for amd64, i386, and pc98.[4]

They were also added to DragonFly BSD on 2009-04-07,[5] before being released in DragonFly BSD 2.3.1 (which strangely seems to have no release notes).[6]

The commit adding the constants to DragonFly BSD states that the commit contents were obtained from FreeBSD.[5] So chronologically FreeBSD is listed before DragonFly BSD. And the commit adding them to FreeBSD references their implementation in OpenSolaris.[3] So chronologically Solaris is listed before FreeBSD.

POSIX.1-2024 is also moved to the end of the list, since it was released decades after any system discussed here.

[1] Bonwick, Jeff (12 Dec 2005). "SEEK_HOLE and SEEK_DATA for sparse files". Jeff Bonwick's Weblog. Archived on 25 Oct 2006.
<https://web.archive.org/web/20061025161241/http://blogs.sun.com/bonwick/entry/seek_hole_and_seek_data>
[2] Oracle (Dec 2005). "Solaris 10 Release Notes".
<https://docs.oracle.com/cd/E19253-01/html/817-0552/index.html>
[3] Dawidek, Pawel Jakub (5 Apr 2007). "Implement SEEK_DATA and SEEK_HOLE extensions to lseek(2) as found in". FreeBSD source tree (Git repository).
<https://cgit.freebsd.org/src/commit/?id=f6521d1c31810b096dd15afff12cf194d1989a0a>
[4] The FreeBSD Project (15 May 2021). "FreeBSD 7.0-RELEASE Release Notes". Section 2.2.5 "File Systems".
<https://www.freebsd.org/releases/7.0R/relnotes>
[5] Avalos, Peter (7 Apr 2009). "Clean up sysconf and associated headers". DragonFly Project Source (Git repository).
<https://gitweb.dragonflybsd.org/dragonfly.git/commit/9d66746cf7a1da0544550266a1c5cb53e776aa01>
[6] Schubert, Simon (7 May 2009). "Roll DragonFly 2.3.1". DragonFly Project Source (Git repository).
<https://gitweb.dragonflybsd.org/dragonfly.git/commit/33a70342dc4e7f9a4ad7c120a827234a33153ca4>

---
 man/man2/lseek.2 | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)
man/man2/lseek.2 +4 -2
index 7d6fe98a3869..d42e39e887db 100644
@@ -210,8 +210,10 @@ .SH HISTORY
 .B SEEK_DATA
 .TQ
 .B SEEK_HOLE
-POSIX.1-2024;
-Solaris, FreeBSD, DragonFly BSD.
+Solaris 10,
+FreeBSD 7.0,
+DragonFly BSD 2.3.1,
+POSIX.1-2024.
 .SH NOTES
 See
 .BR open (2)
Signature · 1 line
2.47.3
#7 lore raw

Re: [PATCH v1 06/21] man/man2/lseek.2: HISTORY: Update appearances of SEEK_{DATA,HOLE}

[minor point on English usage]

Hi Seth,

Quoted 3 lines · Seth McDonald

SEEK_DATA and SEEK_HOLE appeared in Solaris no later than 2005-12-12, when a ZFS developer stated in a blog post that "[a]t this [time of] writing, SEEK_HOLE and SEEK_DATA are Solaris-specific."[1]

"At this writing" is idiomatic (but relatively formal) English.

If the bracketed "[time of]" was meant only or mainly to clarify meaning for non-native English speakers, of whom there are many subscribed to this list, that's fine of course, and you should skip this message.

I'm having trouble finding an authoritative source for my claim, and my _American Heritage Dictionary of Idioms_ is no use--possibly because this isn't an idiomatic, but a literal one, if one interprets "writing" as referring to an action in progress, like "playing" or "dancing", and not as a gerund, as in "in my time of dying".

But here are some exhibits of its correct (idiomatic, if you will) use on the Web.

"I also subscribe to MLB-TV and urge on my Baltimore Orioles, who haven't had such a good time of it at this writing."

	https://www.bowdoin.edu/news/2025/06/getting-them-laughing.html

"Linney has a series of audio lectures based on The First Year of Latin, an 1902 text by Gunnison and Harley covering, at this writing, half the text."
https://quarksandquirks.wordpress.com/tag/william-linney/

"The program book, still online at this writing, contained informative program notes by musicologist Anne Piéjus, an excellent essay by Washington Post Art and Architecture critic Philip Kennicott drawing parallels between the French court’s reception of Esther and impacts of today’s social media, and an also excellent essay by music historian Benjamin Bernard who covered private school education at a contemporaneous boys school, Collège Mazarin, and the girls school at Saint-Cyr, Maison royae de Saint-Louis."
https://operagene.com/new-blog/2024/2/12/opera-lafayettes-from-saint-cyr-to-cannons-moreau-and-handels-esther-theater-as-mass-media

(One's got to have an immense lung capacity to perform opera professionally, and even its fans would seem to be up to that high standard, judging by the prodigious length of the foregoing sentence.)

Regards,
Branden

#8 lore raw

PATCH 7/21 man/man2/lseek.2: HISTORY: Update POSIX appearances of lseek(2)

In reply to Seth McDonald

lseek(2) appeared in POSIX.1-1988.[1]

[1] IEEE Std 1003.1-1988, Section 6.5.3 "Reposition Read/Write File Offset".

---
 man/man2/lseek.2 | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
man/man2/lseek.2 +3 -1
index d42e39e887db..3d48088d0aaf 100644
@@ -205,7 +205,9 @@ .SH VERSIONS
 .SH STANDARDS
 POSIX.1-2024.
 .SH HISTORY
-POSIX.1-2001, SVr4, 4.3BSD.
+4.3BSD,
+SVr4,
+POSIX.1-1988.
 .TP
 .B SEEK_DATA
 .TQ
Signature · 1 line
2.47.3
#9 lore raw

PATCH 8/21 man/man2/mincore.2: HISTORY: Update appearances of mincore(2)

In reply to Seth McDonald

mincore(2) was implemented in FreeBSD on 1995-10-21,[1] which was first included in the FreeBSD 2.2 release on 1997-03.[2]

It was implemented in NetBSD on 1999-06-15,[3] which was first included in the NetBSD 1.5 release on 2000-12-06,[4] (despite the commit message stating its intended inclusion in NetBSD 1.4.1).

It was implemented in OpenBSD on 2001-03-09,[5] which was first included in the OpenBSD 2.9 release on 2001-06-01.[6]

All other listed systems are taken at face value and rearranged in chronological-ish order.

[1] Dyson, John (21 Oct 1995). "Implement mincore system call." FreeBSD source tree (Git repository).
<https://cgit.freebsd.org/src/commit/?id=02c04a2f6c83ee28ed637d120296d04da8f03372>
[2] The FreeBSD Project (29 Nov 2025). "Prior Releases – EOL".
<https://www.freebsd.org/releases>
[3] Thorpe, Jason (15 Jun 1999). "Several changes, developed and tested concurrently:". NetBSD src (CVS repository).
<https://cvsweb.netbsd.org/bsdweb.cgi/src/sys/uvm/uvm_mmap.c?rev=1.22>
[4] The NetBSD Foundation (2026). "History of NetBSD releases".
<https://www.netbsd.org/releases/formal.html>
[5] art (9 Mar 2001). "More syncing to NetBSD." OpenBSD src (CVS repository).
<https://cvsweb.openbsd.org/src/sys/uvm/uvm_mmap.c?rev=1.7&content-type=text/x-cvsweb-markup>
[6] de Raadt, Theo (1 Jun 2001). "OpenBSD 2.9".
<https://www.openbsd.org/29.html>

---
 man/man2/mincore.2 | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)
man/man2/mincore.2 +8 -5
index 8574ed1922d9..a9a1974466a6 100644
@@ -112,13 +112,16 @@ .SH ERRORS
 .SH STANDARDS
 None.
 .SH HISTORY
+SunOS 4.1,
+4.4BSD,
+FreeBSD 2.2,
+Solaris 8,
 Linux 2.3.99pre1,
-glibc 2.2.
+glibc 2.2,
+NetBSD 1.5,
+OpenBSD 2.9,
+AIX 5.1.
 .P
-First appeared in 4.4BSD.
-.P
-NetBSD, FreeBSD, OpenBSD, Solaris 8,
-AIX 5.1, SunOS 4.1.
 .SH BUGS
 Before Linux 2.6.21,
 .BR mincore ()
Signature · 1 line
2.47.3
#10 lore raw

Re: [PATCH v1 08/21] man/man2/mincore.2: HISTORY: Update appearances of mincore(2)

Hi Seth,

Quoted 2 lines · Seth McDonald

mincore(2) was implemented in FreeBSD on 1995-10-21,[1] which was first included in the FreeBSD 2.2 release on 1997-03.[2]

Sorry for taking so much time to respond. I was busy with a meeting of the C Committee. I'm back. I've merged already patches 01..07.

This patch seems to be corrupt.

warning: quoted CRLF detected
Applying: man/man2/mincore.2: HISTORY: Update appearances of mincore(2)
error: patch failed: man/man2/mincore.2:112
error: man/man2/mincore.2: patch does not apply
Patch failed at 0001 man/man2/mincore.2: HISTORY: Update appearances of mincore(2)
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false" Press any key to continue...

I could manually apply it, but it's probably worth checking why this is happening. Probably another issue with protonmail, I guess.

Have a lovely night!
Alex

Quoted 61 lines

It was implemented in NetBSD on 1999-06-15,[3] which was first included in the NetBSD 1.5 release on 2000-12-06,[4] (despite the commit message stating its intended inclusion in NetBSD 1.4.1).

It was implemented in OpenBSD on 2001-03-09,[5] which was first included in the OpenBSD 2.9 release on 2001-06-01.[6]

All other listed systems are taken at face value and rearranged in chronological-ish order.

[1] Dyson, John (21 Oct 1995). "Implement mincore system call." FreeBSD source tree (Git repository).
<https://cgit.freebsd.org/src/commit/?id=02c04a2f6c83ee28ed637d120296d04da8f03372>
[2] The FreeBSD Project (29 Nov 2025). "Prior Releases – EOL".
<https://www.freebsd.org/releases>
[3] Thorpe, Jason (15 Jun 1999). "Several changes, developed and tested concurrently:". NetBSD src (CVS repository).
<https://cvsweb.netbsd.org/bsdweb.cgi/src/sys/uvm/uvm_mmap.c?rev=1.22>
[4] The NetBSD Foundation (2026). "History of NetBSD releases".
<https://www.netbsd.org/releases/formal.html>
[5] art (9 Mar 2001). "More syncing to NetBSD." OpenBSD src (CVS repository).
<https://cvsweb.openbsd.org/src/sys/uvm/uvm_mmap.c?rev=1.7&content-type=text/x-cvsweb-markup>
[6] de Raadt, Theo (1 Jun 2001). "OpenBSD 2.9".
<https://www.openbsd.org/29.html>

---
 man/man2/mincore.2 | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)
man/man2/mincore.2 +8 -5
index 8574ed1922d9..a9a1974466a6 100644
@@ -112,13 +112,16 @@ .SH ERRORS
 .SH STANDARDS
 None.
 .SH HISTORY
+SunOS 4.1,
+4.4BSD,
+FreeBSD 2.2,
+Solaris 8,
 Linux 2.3.99pre1,
-glibc 2.2.
+glibc 2.2,
+NetBSD 1.5,
+OpenBSD 2.9,
+AIX 5.1.
 .P
-First appeared in 4.4BSD.
-.P
-NetBSD, FreeBSD, OpenBSD, Solaris 8,
-AIX 5.1, SunOS 4.1.
 .SH BUGS
 Before Linux 2.6.21,
 .BR mincore ()
Signature · 1 line
2.47.3
Signature · 1 line
<https://www.alejandro-colomar.es>
#11 lore raw

PATCH 9/21 man/man2/mkdir.2: HISTORY: Change order of mkdirat(2)

In reply to Seth McDonald

glibc 2.4 released on 2006-03-06.[1] Linux 2.6.16 released on 2006-03-20.[2] So chronologically list glibc before Linux.

POSIX.1-2008 released in 2008, adding mkdirat(2) to the specification.[3] glibc added mkdirat(2) on 2005-12-03,[4] and the mailing list discussion about its addition seems to suggest it was considered before it was known that POSIX would add it.[5] So chronologically list glibc (and Linux) before POSIX.

[1] McGrath, Roland (6 Mar 2006). "GNU C Library version 2.4 release". info-gnu (Mailing list).
<https://lists.gnu.org/archive/html/info-gnu/2006-03/msg00000.html>
[2] Linux Kernel Distribution System (20 Mar 2006). "Linux kernel 2.6.16 released". linux-kernel-announce (Mailing list).
<https://lore.kernel.org/linux-kernel-announce/[email protected]>
[3] IEEE Std 1003.1-2008, Volume 2, Chapter 3 "System Interfaces", pp. 1289-1291.
<https://pubs.opengroup.org/onlinepubs/9699919799.2008edition/functions/mkdir.html>
[4] Drepper, Ulrich (3 Dec 2005). "* io/Makefile (routines): Add mknodat, xmknodat, mkdirat, mkfifoat." GNU C Library master sources (Git repository).
<https://sourceware.org/git/?p=glibc.git;a=commit;h=e186c703dc073b8be95d0bf893bb8ebb127fe02b>
[5] Meyering, Jim (30 Nov 2005). "FYI: new openat-like function:
mkdirat". libc-alpha (Mailing list).
<https://sourceware.org/pipermail/libc-alpha/2005-November/019749.html>

---
 man/man2/mkdir.2 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
man/man2/mkdir.2 +2 -2
index ac0d4405ecb8..263dee5c0556 100644
@@ -234,9 +234,9 @@ .SH HISTORY
 .\" SVr4 documents additional EIO, EMULTIHOP
 .TP
 .BR mkdirat ()
-POSIX.1-2008.
+glibc 2.4,
 Linux 2.6.16,
-glibc 2.4.
+POSIX.1-2008.
 .SH NOTES
 There are many infelicities in the protocol underlying NFS.
 Some of these affect
Signature · 1 line
2.47.3
#12 lore raw

PATCH 10/21 man/man2/mkdir.2: HISTORY: Update BSD and POSIX appearances of mkdir(2)

In reply to Seth McDonald

mkdir(2) seems to have appeared in 4.2BSD with the system call number 136, as seen in the system's /usr/src/sys/sys/syscalls.c file.[1] The function also appeared in POSIX.1-1988.[2]

[1] Spinellis, Diomidis (5 Jan 2026). Unix History Repository (Git repository). Tag "BSD-4_2".
<https://github.com/dspinellis/unix-history-repo/tree/BSD-4_2>
[2] IEEE Std 1003.1-1988, Section 5.4.1 "Make a Directory".

---
 man/man2/mkdir.2 | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
man/man2/mkdir.2 +3 -1
index 263dee5c0556..c6d1b0a887e3 100644
@@ -230,7 +230,9 @@ .SH STANDARDS
 .SH HISTORY
 .TP
 .BR mkdir ()
-SVr4, BSD, POSIX.1-2001.
+4.2BSD,
+SVr4,
+POSIX.1-1988.
 .\" SVr4 documents additional EIO, EMULTIHOP
 .TP
 .BR mkdirat ()
Signature · 1 line
2.47.3
#13 lore raw

PATCH 11/21 man/man2/mknod.2: HISTORY: Change order of mknodat(2)

In reply to Seth McDonald

glibc 2.4 released on 2006-03-06.[1] Linux 2.6.16 released on 2006-03-20.[2] So chronologically list glibc before Linux.

POSIX.1-2008 released in 2008, adding mkdirat(2) as an XSI extension.[3] glibc added mknodat(2) on 2005-12-03.[4] So chronologically list glibc (and Linux) before POSIX.

[1] McGrath, Roland (6 Mar 2006). "GNU C Library version 2.4 release". info-gnu (Mailing list).
<https://lists.gnu.org/archive/html/info-gnu/2006-03/msg00000.html>
[2] Linux Kernel Distribution System (20 Mar 2006). "Linux kernel 2.6.16 released". linux-kernel-announce (Mailing list).
<https://lore.kernel.org/linux-kernel-announce/[email protected]>
[3] IEEE Std 1003.1-2008, Volume 2, Chapter 3 "System Interfaces", pp. 1298-1301.
<https://pubs.opengroup.org/onlinepubs/9699919799.2008edition/functions/mknod.html>
[4] Drepper, Ulrich (3 Dec 2005). "* io/Makefile (routines): Add mknodat, xmknodat, mkdirat, mkfifoat." GNU C Library master sources (Git repository).
<https://sourceware.org/git/?p=glibc.git;a=commit;h=e186c703dc073b8be95d0bf893bb8ebb127fe02b>

---
 man/man2/mknod.2 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
man/man2/mknod.2 +2 -2
index 1faa936800ad..4a9aa9f6128a 100644
@@ -272,9 +272,9 @@ .SH HISTORY
 .\" EMULTIHOP, ENOLINK, or EINTR error is documented.
 .TP
 .BR mknodat ()
+glibc 2.4,
 Linux 2.6.16,
-glibc 2.4.
-POSIX.1-2008.
+POSIX.1-2008 XSI.
 .SH NOTES
 There are many infelicities in the protocol underlying NFS.
 Some of these affect
Signature · 1 line
2.47.3
#14 lore raw

PATCH 12/21 man/man2/mknod.2: HISTORY: Update POSIX appearances of mknod(2)

In reply to Seth McDonald

mknod(2) appeared in SUSv1.[1] The function was added to POSIX.1-2001 when POSIX and SUS merged, but as an XSI extension (still SUS-only).[2]

[1] X/Open CAE Specification, System Interfaces and Headers Issue 4, Version 2, Chapter 3 "System Interfaces", pp. 392-393.
[2] IEEE Std 1003.1-2001, Volume 2, Chapter 3 "System Interfaces", pp. 758-760.
<https://pubs.opengroup.org/onlinepubs/009604499/functions/mknod.html>

---
 man/man2/mknod.2 | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)
man/man2/mknod.2 +4 -1
index 4a9aa9f6128a..f628ee5afe8d 100644
@@ -266,7 +266,10 @@ .SH STANDARDS
 .SH HISTORY
 .TP
 .BR mknod ()
-SVr4, 4.4BSD, POSIX.1-2001 (but see VERSIONS).
+SVr4,
+4.4BSD,
+SUSv1,
+POSIX.1-2001 XSI (but see VERSIONS).
 .\" The Linux version differs from the SVr4 version in that it
 .\" does not require root permission to create pipes, also in that no
 .\" EMULTIHOP, ENOLINK, or EINTR error is documented.
Signature · 1 line
2.47.3
#15 lore raw

PATCH 13/21 man/man2/mknod.2: STANDARDS: Update

In reply to Seth McDonald

mknod(2) and mknodat(2) are specified in POSIX.1-2024 as an XSI extension.[1]

[1] IEEE Std 1003.1-2024, Volume 2, Chapter 3 "System Interfaces", pp. 1421-1424.
<https://pubs.opengroup.org/onlinepubs/9799919799/functions/mknod.html>

---
 man/man2/mknod.2 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
man/man2/mknod.2 +1 -1
index f628ee5afe8d..b506db246d01 100644
@@ -262,7 +262,7 @@ .SH VERSIONS
 .BR mkdir (2).
 .\" and one should make UNIX domain sockets with socket(2) and bind(2).
 .SH STANDARDS
-POSIX.1-2024.
+POSIX.1-2024 XSI.
 .SH HISTORY
 .TP
 .BR mknod ()
Signature · 1 line
2.47.3
#16 lore raw

PATCH 14/21 man/man2/mlock.2: HISTORY: Update POSIX appearances of m(un)lock(all)(2)

In reply to Seth McDonald

mlock(2), munlock(2), mlockall(2), and munlockall(2) appeared in POSIX.1-1996.[1][2]

[1] ISO/IEC 9945-1:1996, Section 12.1.1 "Lock/Unlock the Address Space of a Process".
[2] ISO/IEC 9945-1:1996, Section 12.1.2 "Lock/Unlock a Range of Process Address Space".

---
 man/man2/mlock.2 | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
man/man2/mlock.2 +2 -1
index 063dde4d4ed2..0222e63a1239 100644
@@ -343,7 +343,8 @@ .SH HISTORY
 .BR mlockall ()
 .TQ
 .BR munlockall ()
-POSIX.1-2001, POSIX.1-2008, SVr4.
+SVr4,
+POSIX.1-1996.
 .TP
 .BR mlock2 ()
 Linux 4.4,
Signature · 1 line
2.47.3
#17 lore raw

PATCH 15/21 man/man2/mmap.2: HISTORY: Update POSIX appearances of m(un)map(2)

In reply to Seth McDonald

mmap(2) and munmap(2) appeared in SUSv1.[1] The functions were then added to POSIX.1-1996.[2][3]

[1] X/Open CAE Specification, System Interfaces and Headers Issue 4, Version 2, Chapter 3 "System Interfaces", pp. 398-400, 414.
[2] ISO/IEC 9945-1:1996, Section 12.2.1 "Map Process Addresses to a Memory Object".
[3] ISO/IEC 9945-1:1996, Section 12.2.2 "Unmap Previously Mapped Addresses".

---
 man/man2/mmap.2 | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)
man/man2/mmap.2 +4 -1
index 093b0caf19c7..4e893501a947 100644
@@ -737,7 +737,10 @@ .SS C library/kernel differences
 .SH STANDARDS
 POSIX.1-2024.
 .SH HISTORY
-POSIX.1-2001, SVr4, 4.4BSD.
+SVr4,
+4.4BSD,
+SUSv1,
+POSIX.1-1996.
 .\" SVr4 documents additional error codes ENXIO and ENODEV.
 .\" SUSv2 documents additional error codes EMFILE and EOVERFLOW.
 .P
Signature · 1 line
2.47.3
#18 lore raw

PATCH 16/21 man/man2/{mount_setattr,move_mount}.2: HISTORY: ffix

In reply to Seth McDonald

Commas are more consistent with other man pages.

---
 man/man2/mount_setattr.2 | 2 +-
 man/man2/move_mount.2    | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
man/man2/mount_setattr.2 +1 -1
index e02c84f43214..882ec031f504 100644
@@ -572,7 +572,7 @@ .SH ERRORS
 .SH STANDARDS
 Linux.
 .SH HISTORY
-Linux 5.12.
+Linux 5.12,
 .\" commit 7d6beb71da3cc033649d641e1e608713b8220290
 .\" commit 2a1867219c7b27f928e2545782b86daaf9ad50bd
 .\" commit 9caccd41541a6f7d6279928d9f971f6642c361af
man/man2/move_mount.2 +1 -1
index 335f4ef548fd..b95191d5ba83 100644
@@ -517,7 +517,7 @@ .SH ERRORS
 .SH STANDARDS
 Linux.
 .SH HISTORY
-Linux 5.2.
+Linux 5.2,
 .\" commit 2db154b3ea8e14b04fee23e3fdfd5e9d17fbc6ae
 .\" commit 400913252d09f9cfb8cce33daee43167921fc343
 glibc 2.36.
Signature · 1 line
2.47.3
#19 lore raw

PATCH 17/21 man/man2/mprotect.2: HISTORY: Update POSIX appearances of mprotect(2)

In reply to Seth McDonald

mprotect(2) appeared in SUSv1.[1] The function was then added to POSIX.1-1996.[2]

[1] X/Open CAE Specification, System Interfaces and Headers Issue 4, Version 2, Chapter 3 "System Interfaces", p. 402.
[2] ISO/IEC 9945-1:1996, Section 12.2.3 "Change Memory Protection".

---
 man/man2/mprotect.2 | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
man/man2/mprotect.2 +3 -1
index 09cec72b76c5..a83971d2f174 100644
@@ -265,7 +265,9 @@ .SH STANDARDS
 .SH HISTORY
 .TP
 .BR mprotect ()
-POSIX.1-2001, SVr4.
+SVr4,
+SUSv1,
+POSIX.1-1996.
 .TP
 .BR pkey_mprotect ()
 Linux 4.9,
Signature · 1 line
2.47.3
#20 lore raw

PATCH 18/21 man/man2/msgctl.2: STANDARDS, HISTORY: Update POSIX appearances of msgctl(2)

In reply to Seth McDonald

msgctl(2) appeared in SUSv1.[1] The function was added to POSIX.1-2001 when POSIX and SUS merged, but as an XSI extension (still SUS-only).[2] And it remains an XSI extension in POSIX.1-2024.[3]

[1] X/Open CAE Specification, System Interfaces and Headers Issue 4, Version 2, Chapter 3 "System Interfaces", pp. 404-405.
[2] IEEE Std 1003.1-2001, Volume 2, Chapter 3 "System Interfaces", pp. 802-803.
<https://pubs.opengroup.org/onlinepubs/009604499/functions/msgctl.html>
[3] IEEE Std 1003.1-2024, Volume 2, Chapter 3 "System Interfaces", pp. 1471-1472.
<https://pubs.opengroup.org/onlinepubs/9799919799/functions/msgctl.html>

---
 man/man2/msgctl.2 | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)
man/man2/msgctl.2 +4 -2
index cff83924ab25..b63ed2cc2e93 100644
@@ -378,9 +378,11 @@ .SH ERRORS
 .B CAP_SYS_RESOURCE
 capability).
 .SH STANDARDS
-POSIX.1-2024.
+POSIX.1-2024 XSI.
 .SH HISTORY
-POSIX.1-2001, SVr4.
+SVr4,
+SUSv1,
+POSIX.1-2001 XSI.
 .\" SVID does not document the EIDRM error condition.
 .P
 Various fields in the
Signature · 1 line
2.47.3
#21 lore raw

PATCH 19/21 man/man2/msgget.2: STANDARDS, HISTORY: Update POSIX appearances of msgget(2)

In reply to Seth McDonald

msgget(2) appeared in SUSv1.[1] The function was added to POSIX.1-2001 when POSIX and SUS merged, but as an XSI extension (still SUS-only).[2] And it remains an XSI extension in POSIX.1-2024.[3]

[1] X/Open CAE Specification, System Interfaces and Headers Issue 4, Version 2, Chapter 3 "System Interfaces", pp. 406-407.
[2] IEEE Std 1003.1-2001, Volume 2, Chapter 3 "System Interfaces", pp. 804-805.
<https://pubs.opengroup.org/onlinepubs/009604499/functions/msgget.html>
[3] IEEE Std 1003.1-2024, Volume 2, Chapter 3 "System Interfaces", pp. 1473-1474.
<https://pubs.opengroup.org/onlinepubs/9799919799/functions/msgget.html>

---
 man/man2/msgget.2 | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)
man/man2/msgget.2 +4 -2
index 8600d66810ea..7bb389790d49 100644
@@ -158,9 +158,11 @@ .SH ERRORS
 .RB ( MSGMNI )
 would be exceeded.
 .SH STANDARDS
-POSIX.1-2024.
+POSIX.1-2024 XSI.
 .SH HISTORY
-POSIX.1-2001, SVr4.
+SVr4,
+SUSv1,
+POSIX.1-2001 XSI.
 .SS Linux
 Until Linux 2.3.20, Linux would return
 .B EIDRM
Signature · 1 line
2.47.3
#22 lore raw

PATCH 20/21 man/man2/msgop.2: STANDARDS, HISTORY: Update POSIX appearances of msg{rcv,snd}(2)

In reply to Seth McDonald

msgrcv(2) and msgsnd(2) appeared in SUSv1.[1] The functions were added to POSIX.1-2001 when POSIX and SUS merged, but as an XSI extension (still SUS-only).[2][3] And they remain as an XSI extension in POSIX.1-2024.[4][5]

[1] X/Open CAE Specification, System Interfaces and Headers Issue 4, Version 2, Chapter 3 "System Interfaces", pp. 408-411.
[2] IEEE Std 1003.1-2001, Volume 2, Chapter 3 "System Interfaces", pp. 806-808.
<https://pubs.opengroup.org/onlinepubs/009604499/functions/msgrcv.html>
[3] IEEE Std 1003.1-2001, Volume 2, Chapter 3 "System Interfaces", pp. 809-811.
<https://pubs.opengroup.org/onlinepubs/009604499/functions/msgsnd.html>
[4] IEEE Std 1003.1-2024, Volume 2, Chapter 3 "System Interfaces", pp. 1475-1477.
<https://pubs.opengroup.org/onlinepubs/9799919799/functions/msgrcv.html>
[5] IEEE Std 1003.1-2024, Volume 2, Chapter 3 "System Interfaces", pp. 1478-1480.
<https://pubs.opengroup.org/onlinepubs/9799919799/functions/msgsnd.html>

---
 man/man2/msgop.2 | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)
man/man2/msgop.2 +4 -2
index 4a5070f05a57..80d557024a77 100644
@@ -440,7 +440,7 @@ .SH ERRORS
 and this kernel was configured without
 .BR CONFIG_CHECKPOINT_RESTORE .
 .SH STANDARDS
-POSIX.1-2024.
+POSIX.1-2024 XSI.
 .P
 The
 .B MSG_EXCEPT
@@ -452,7 +452,9 @@ .SH STANDARDS
 .\" MSG_COPY since glibc 2.18
 feature test macro.
 .SH HISTORY
-POSIX.1-2001, SVr4.
+SVr4,
+SUSv1,
+POSIX.1-2001 XSI.
 .P
 The
 .I msgp
Signature · 1 line
2.47.3
#23 lore raw

PATCH 21/21 man/man2/msync.2: HISTORY: Update POSIX appearances of msync(2)

In reply to Seth McDonald

msync(2) appeared in SUSv1.[1] The function was then added to POSIX.1-1996.[2]

[1] X/Open CAE Specification, System Interfaces and Headers Issue 4, Version 2, Chapter 3 "System Interfaces", pp. 412-413.
[2] ISO/IEC 9945-1:1996, Section 12.2.4 "Memory Object Synchronization".

---
 man/man2/msync.2 | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
man/man2/msync.2 +2 -1
index 09b8ecb127ef..94b458041703 100644
@@ -113,7 +113,8 @@ .SH VERSIONS
 .SH STANDARDS
 POSIX.1-2024.
 .SH HISTORY
-POSIX.1-2001.
+SUSv1,
+POSIX.1-1996.
 .P
 This call was introduced in Linux 1.3.21, and then used
 .B EFAULT
Signature · 1 line
2.47.3
#24 lore raw

the origin of mkdir(2) (was: [PATCH v1 00/21] man/man2/*: Update history of syscalls H-M)

In reply to Seth McDonald

Hi Seth,

Quoted 7 lines · Seth McDonald

This set updates the history of system calls H to M.

While I have been thorough with my research, I would encourage those interested to double-check that my edits make sense given the listed sources. Particularly for linkat(2), SEEK_DATA/SEEK_HOLE, mkdirat(2), and mincore(2), since they took significantly more time and research than other functions.

I thank you for this work! I could not have told you that mkdir(2)-- the system call--arrived in Unix as late as 4.2BSD. My first thought was, "that can't be right". My second was, "ah, that must be when Unix got rid of the 14-character limit on file names".

(Traditionally in Unix, a directory was a plain file of 16-byte entries--a 14-byte char field for the file name, which was not null-terminated if of maximum length, and a 2-byte int for the file's inode number. This design kept the system call interface narrow. It also, if I understand the war stories correctly, could lead to horrible problems, like users open(2)ing directories belonging to themselves and trashing them with sloppy code, or introducing cycles into into the graph of the file system by creating hard links to directories.[1])

And sure enough, history appears to record that the Berkeley FFS ("fast file system") came in with 4.2BSD as well.

https://www.oreilly.com/openbook/opensources/book/kirkmck.html

Regards,
Branden

[1] This was such an unthinkable and invalid situation that, again AIUI, that rather than being flatly prohibited by the kernel, only root was allowed to create hard links to directories.

#25 lore raw
In reply to Seth McDonald

Hi Seth,

Quoted 11 lines · Seth McDonald

Hi all,

This set updates the history of system calls H to M.

While I have been thorough with my research, I would encourage those interested to double-check that my edits make sense given the listed sources. Particularly for linkat(2), SEEK_DATA/SEEK_HOLE, mkdirat(2), and mincore(2), since they took significantly more time and research than other functions.

Seth McDonald (21):

I've applied all patches, except the mincore.2 one (it was corrupt). Thanks a lot! I'll release very soon; probably tomorrow. :)

Have a lovely night!
Alex

Quoted 73 lines

man/man2/ioctl_eventpoll.2: HISTORY: ffix man/man2/kill.2: HISTORY: Update POSIX appearances of kill(2) man/man2/link.2: HISTORY: Change order of linkat(2) man/man2/link.2: HISTORY: Update POSIX appearances of link(2) man/man2/listen.2: HISTORY: Change order man/man2/lseek.2: HISTORY: Update appearances of SEEK_{DATA,HOLE} man/man2/lseek.2: HISTORY: Update POSIX appearances of lseek(2) man/man2/mincore.2: HISTORY: Update appearances of mincore(2) man/man2/mkdir.2: HISTORY: Change order of mkdirat(2) man/man2/mkdir.2: HISTORY: Update BSD and POSIX appearances of

    mkdir(2)
  man/man2/mknod.2: HISTORY: Change order of mknodat(2)
  man/man2/mknod.2: HISTORY: Update POSIX appearances of mknod(2)
  man/man2/mknod.2: STANDARDS: Update
  man/man2/mlock.2: HISTORY: Update POSIX appearances of
    m(un)lock(all)(2)
  man/man2/mmap.2: HISTORY: Update POSIX appearances of m(un)map(2)
  man/man2/{mount_setattr,move_mount}.2: HISTORY: ffix
  man/man2/mprotect.2: HISTORY: Update POSIX appearances of mprotect(2)
  man/man2/msgctl.2: STANDARDS, HISTORY: Update POSIX appearances of
    msgctl(2)
  man/man2/msgget.2: STANDARDS, HISTORY: Update POSIX appearances of
    msgget(2)
  man/man2/msgop.2: STANDARDS, HISTORY: Update POSIX appearances of
    msg{rcv,snd}(2)

man/man2/msync.2: HISTORY: Update POSIX appearances of msync(2)

 man/man2/ioctl_eventpoll.2 |  2 +-
 man/man2/kill.2            |  4 +++-
 man/man2/link.2            | 10 ++++++----
 man/man2/listen.2          |  4 ++--
 man/man2/lseek.2           | 10 +++++++---
 man/man2/mincore.2         | 13 ++++++++-----
 man/man2/mkdir.2           |  8 +++++---
 man/man2/mknod.2           | 11 +++++++----
 man/man2/mlock.2           |  3 ++-
 man/man2/mmap.2            |  5 ++++-
 man/man2/mount_setattr.2   |  2 +-
 man/man2/move_mount.2      |  2 +-
 man/man2/mprotect.2        |  4 +++-
 man/man2/msgctl.2          |  6 ++++--
 man/man2/msgget.2          |  6 ++++--
 man/man2/msgop.2           |  6 ++++--
 man/man2/msync.2           |  3 ++-
 17 files changed, 64 insertions(+), 35 deletions(-)

Range-diff against v0:

 -:  ------------ >  1:  d109f3dc06e2 man/man2/ioctl_eventpoll.2: HISTORY: ffix
 -:  ------------ >  2:  55de16b213bf man/man2/kill.2: HISTORY: Update POSIX appearances of kill(2)
 -:  ------------ >  3:  17eacf0f2d3e man/man2/link.2: HISTORY: Change order of linkat(2)
 -:  ------------ >  4:  bec317b8ee88 man/man2/link.2: HISTORY: Update POSIX appearances of link(2)
 -:  ------------ >  5:  2024c82a058d man/man2/listen.2: HISTORY: Change order
 -:  ------------ >  6:  bcf9f5113f3c man/man2/lseek.2: HISTORY: Update appearances of SEEK_{DATA,HOLE}
 -:  ------------ >  7:  2dd12d136bf0 man/man2/lseek.2: HISTORY: Update POSIX appearances of lseek(2)
 -:  ------------ >  8:  817af323707e man/man2/mincore.2: HISTORY: Update appearances of mincore(2)
 -:  ------------ >  9:  8b25a256e60f man/man2/mkdir.2: HISTORY: Change order of mkdirat(2)
 -:  ------------ > 10:  347e36c11666 man/man2/mkdir.2: HISTORY: Update BSD and POSIX appearances of mkdir(2)
 -:  ------------ > 11:  d3da8260e1bc man/man2/mknod.2: HISTORY: Change order of mknodat(2)
 -:  ------------ > 12:  b0feda20f21d man/man2/mknod.2: HISTORY: Update POSIX appearances of mknod(2)
 -:  ------------ > 13:  32bd25fd3630 man/man2/mknod.2: STANDARDS: Update
 -:  ------------ > 14:  67bf0c1aa133 man/man2/mlock.2: HISTORY: Update POSIX appearances of m(un)lock(all)(2)
 -:  ------------ > 15:  57292b4f60c4 man/man2/mmap.2: HISTORY: Update POSIX appearances of m(un)map(2)
 -:  ------------ > 16:  b8f4e6fa54e7 man/man2/{mount_setattr,move_mount}.2: HISTORY: ffix
 -:  ------------ > 17:  4e1acc0f5e00 man/man2/mprotect.2: HISTORY: Update POSIX appearances of mprotect(2)
 -:  ------------ > 18:  024ce32c9da5 man/man2/msgctl.2: STANDARDS, HISTORY: Update POSIX appearances of msgctl(2)
 -:  ------------ > 19:  975e61bea29f man/man2/msgget.2: STANDARDS, HISTORY: Update POSIX appearances of msgget(2)
 -:  ------------ > 20:  86e7c24b1428 man/man2/msgop.2: STANDARDS, HISTORY: Update POSIX appearances of msg{rcv,snd}(2)
 -:  ------------ > 21:  d106bca86ec1 man/man2/msync.2: HISTORY: Update POSIX appearances of msync(2)

base-commit: 6754bd1a126ed1e9b7d9c2bc1d221681f5182bb3

Signature · 1 line
2.47.3
Signature · 1 line
<https://www.alejandro-colomar.es>
#26 lore raw

v2 cover man/man2/*: Update history of syscalls H-M

In reply to Seth McDonald

Hi Alex,

Apologies on my end also for my delayed response. I've made some large but hopefully beneficial changes to my email workflow – as can be seen with the different email address.

Quoted 2 lines

This patch seems to be corrupt. [...] Probably another issue with protonmail, I guess.

Yeah at this point I give up with ProtonMail. I shouldn't have to fix all their issues for them just to send in a patch. Hopefully Fastmail serves me better.

Anyhow, this is just the patch for mincore(2) with a few minor adjustments on the commit message. I won't PGP sign it yet as I first want to ensure everything works before adding things on top. But if all is well, I'll continue to sign my patches with my more secure key:

E9D1 26A5 F0D4 9DF7 792B C2E2 B4BF 4530 D39B 2D51

Let me know if it's still corrupt, and I'll ̶k̶i̶c̶k̶ ̶m̶y̶ ̶P̶C calmly figure out what's going on.

Seth McDonald (1):
man/man2/mincore.2: HISTORY: Update appearances of mincore(2)

 man/man2/mincore.2 | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

Range-diff against v1:

 1:  d109f3dc06e2 <  -:  ------------ man/man2/ioctl_eventpoll.2: HISTORY: ffix
 2:  55de16b213bf <  -:  ------------ man/man2/kill.2: HISTORY: Update POSIX appearances of kill(2)
 3:  17eacf0f2d3e <  -:  ------------ man/man2/link.2: HISTORY: Change order of linkat(2)
 4:  bec317b8ee88 <  -:  ------------ man/man2/link.2: HISTORY: Update POSIX appearances of link(2)
 5:  2024c82a058d <  -:  ------------ man/man2/listen.2: HISTORY: Change order
 6:  bcf9f5113f3c <  -:  ------------ man/man2/lseek.2: HISTORY: Update appearances of SEEK_{DATA,HOLE}
 7:  2dd12d136bf0 <  -:  ------------ man/man2/lseek.2: HISTORY: Update POSIX appearances of lseek(2)
 8:  817af323707e !  1:  b1b6f011a7d3 man/man2/mincore.2: HISTORY: Update appearances of mincore(2)

@@ Metadata
## Commit message ##
man/man2/mincore.2: HISTORY: Update appearances of mincore(2)

- mincore(2) was implemented in FreeBSD on 1995-10-21,[1] which was first
+ mincore(2) was implemented in FreeBSD on 1995-10-21,[1] and was first
included in the FreeBSD 2.2 release on 1997-03.[2]

- It was implemented in NetBSD on 1999-06-15,[3] which was first included
- in the NetBSD 1.5 release on 2000-12-06,[4] (despite the commit message
+ It was implemented in NetBSD on 1999-06-15,[3] and was first included in
+ the NetBSD 1.5 release on 2000-12-06,[4] (despite the commit message
stating its intended inclusion in NetBSD 1.4.1).

- It was implemented in OpenBSD on 2001-03-09,[5] which was first included
+ It was implemented in OpenBSD on 2001-03-09,[5] and was first included
in the OpenBSD 2.9 release on 2001-06-01.[6]

All other listed systems are taken at face value and rearranged in chronological-ish order.

[1] Dyson, John (21 Oct 1995). "Implement mincore system call."
- FreeBSD source tree (Git repository).
- <https://cgit.freebsd.org/src/commit/?id=02c04a2f6c83ee28ed637d120296d04da8f03372>
+ FreeBSD source tree (Git repository). Commit
+ 02c04a2f6c83ee28ed637d120296d04da8f03372.
[2] The FreeBSD Project (29 Nov 2025). "Prior Releases – EOL".
<https://www.freebsd.org/releases>
[3] Thorpe, Jason (15 Jun 1999). "Several changes, developed and tested

 9:  8b25a256e60f <  -:  ------------ man/man2/mkdir.2: HISTORY: Change order of mkdirat(2)
10:  347e36c11666 <  -:  ------------ man/man2/mkdir.2: HISTORY: Update BSD and POSIX appearances of mkdir(2)
11:  d3da8260e1bc <  -:  ------------ man/man2/mknod.2: HISTORY: Change order of mknodat(2)
12:  b0feda20f21d <  -:  ------------ man/man2/mknod.2: HISTORY: Update POSIX appearances of mknod(2)
13:  32bd25fd3630 <  -:  ------------ man/man2/mknod.2: STANDARDS: Update
14:  67bf0c1aa133 <  -:  ------------ man/man2/mlock.2: HISTORY: Update POSIX appearances of m(un)lock(all)(2)
15:  57292b4f60c4 <  -:  ------------ man/man2/mmap.2: HISTORY: Update POSIX appearances of m(un)map(2)
16:  b8f4e6fa54e7 <  -:  ------------ man/man2/{mount_setattr,move_mount}.2: HISTORY: ffix
17:  4e1acc0f5e00 <  -:  ------------ man/man2/mprotect.2: HISTORY: Update POSIX appearances of mprotect(2)
18:  024ce32c9da5 <  -:  ------------ man/man2/msgctl.2: STANDARDS, HISTORY: Update POSIX appearances of msgctl(2)
19:  975e61bea29f <  -:  ------------ man/man2/msgget.2: STANDARDS, HISTORY: Update POSIX appearances of msgget(2)
20:  86e7c24b1428 <  -:  ------------ man/man2/msgop.2: STANDARDS, HISTORY: Update POSIX appearances of msg{rcv,snd}(2)
21:  d106bca86ec1 <  -:  ------------ man/man2/msync.2: HISTORY: Update POSIX appearances of msync(2)

base-commit: e2cc229b7551a63bb51853c849ce1a9e95946637

Signature · 1 line
2.53.0.1
#27 lore raw

PATCH v2 1/1 man/man2/mincore.2: HISTORY: Update appearances of mincore(2)

mincore(2) was implemented in FreeBSD on 1995-10-21,[1] and was first included in the FreeBSD 2.2 release on 1997-03.[2]

It was implemented in NetBSD on 1999-06-15,[3] and was first included in the NetBSD 1.5 release on 2000-12-06,[4] (despite the commit message stating its intended inclusion in NetBSD 1.4.1).

It was implemented in OpenBSD on 2001-03-09,[5] and was first included in the OpenBSD 2.9 release on 2001-06-01.[6]

All other listed systems are taken at face value and rearranged in chronological-ish order.

[1] Dyson, John (21 Oct 1995). "Implement mincore system call." FreeBSD source tree (Git repository). Commit 02c04a2f6c83ee28ed637d120296d04da8f03372.
[2] The FreeBSD Project (29 Nov 2025). "Prior Releases – EOL".
<https://www.freebsd.org/releases>
[3] Thorpe, Jason (15 Jun 1999). "Several changes, developed and tested concurrently:". NetBSD src (CVS repository).
<https://cvsweb.netbsd.org/bsdweb.cgi/src/sys/uvm/uvm_mmap.c?rev=1.22>
[4] The NetBSD Foundation (2026). "History of NetBSD releases".
<https://www.netbsd.org/releases/formal.html>
[5] art (9 Mar 2001). "More syncing to NetBSD." OpenBSD src (CVS repository).
<https://cvsweb.openbsd.org/src/sys/uvm/uvm_mmap.c?rev=1.7&content-type=text/x-cvsweb-markup>
[6] de Raadt, Theo (1 Jun 2001). "OpenBSD 2.9".
<https://www.openbsd.org/29.html>

---
 man/man2/mincore.2 | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)
man/man2/mincore.2 +8 -5
index 3fafdf0c8f76..c3ff474cf654 100644
@@ -114,13 +114,16 @@ .SH ERRORS
 .SH STANDARDS
 None.
 .SH HISTORY
+SunOS 4.1,
+4.4BSD,
+FreeBSD 2.2,
+Solaris 8,
 Linux 2.3.99pre1,
-glibc 2.2.
+glibc 2.2,
+NetBSD 1.5,
+OpenBSD 2.9,
+AIX 5.1.
 .P
-First appeared in 4.4BSD.
-.P
-NetBSD, FreeBSD, OpenBSD, Solaris 8,
-AIX 5.1, SunOS 4.1.
 .SH BUGS
 Before Linux 2.6.21,
 .BR mincore ()
Signature · 1 line
2.53.0.1
#28 lore raw

Re: [PATCH v2 1/1] man/man2/mincore.2: HISTORY: Update appearances of mincore(2)

Hi Seth,

Quoted 29 lines · Seth McDonald

mincore(2) was implemented in FreeBSD on 1995-10-21,[1] and was first included in the FreeBSD 2.2 release on 1997-03.[2]

It was implemented in NetBSD on 1999-06-15,[3] and was first included in the NetBSD 1.5 release on 2000-12-06,[4] (despite the commit message stating its intended inclusion in NetBSD 1.4.1).

It was implemented in OpenBSD on 2001-03-09,[5] and was first included in the OpenBSD 2.9 release on 2001-06-01.[6]

All other listed systems are taken at face value and rearranged in chronological-ish order.

[1] Dyson, John (21 Oct 1995). "Implement mincore system call." FreeBSD source tree (Git repository). Commit 02c04a2f6c83ee28ed637d120296d04da8f03372.
[2] The FreeBSD Project (29 Nov 2025). "Prior Releases – EOL".
<https://www.freebsd.org/releases>
[3] Thorpe, Jason (15 Jun 1999). "Several changes, developed and tested concurrently:". NetBSD src (CVS repository).
<https://cvsweb.netbsd.org/bsdweb.cgi/src/sys/uvm/uvm_mmap.c?rev=1.22>
[4] The NetBSD Foundation (2026). "History of NetBSD releases".
<https://www.netbsd.org/releases/formal.html>
[5] art (9 Mar 2001). "More syncing to NetBSD." OpenBSD src (CVS repository).
<https://cvsweb.openbsd.org/src/sys/uvm/uvm_mmap.c?rev=1.7&content-type=text/x-cvsweb-markup>
[6] de Raadt, Theo (1 Jun 2001). "OpenBSD 2.9".
<https://www.openbsd.org/29.html>

Quoted 1 line

Thanks! I've applied the patch.

I had to amend it with this:

	diff --git i/man/man2/mincore.2 w/man/man2/mincore.2
	index c3ff474cf654..015dd281096c 100644
	--- i/man/man2/mincore.2
	+++ w/man/man2/mincore.2
	@@ -123,7 +123,6 @@ .SH HISTORY
	 NetBSD 1.5,
	 OpenBSD 2.9,
	 AIX 5.1.
	-.P
	 .SH BUGS
	 Before Linux 2.6.21,
	 .BR mincore ()

as CI reported an issue:

...
remote: MANDOC .tmp/man/man2/mincore.2.lint-man.mandoc.touch
remote: mandoc: .tmp/man/man2/mincore.2:126:2: WARNING: skipping paragraph macro: PP empty
remote: make: *** [/home/alx/src/linux/man-pages/man-pages/contrib/share/mk/lint/man/mandoc.mk:30: .tmp/man/man2/mincore.2.lint-man.mandoc.touch] Error 1

You can check <CONTRIBUTING.d/lint> in case you want to check these issues. However, I don't mind sporadic issues in patches, since my CI catches them anyway, so I can just amend them when I find them.

Have a lovely day!
Alex

Quoted 34 lines
---
 man/man2/mincore.2 | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)
man/man2/mincore.2 +8 -5
index 3fafdf0c8f76..c3ff474cf654 100644
@@ -114,13 +114,16 @@ .SH ERRORS
 .SH STANDARDS
 None.
 .SH HISTORY
+SunOS 4.1,
+4.4BSD,
+FreeBSD 2.2,
+Solaris 8,
 Linux 2.3.99pre1,
-glibc 2.2.
+glibc 2.2,
+NetBSD 1.5,
+OpenBSD 2.9,
+AIX 5.1.
 .P
-First appeared in 4.4BSD.
-.P
-NetBSD, FreeBSD, OpenBSD, Solaris 8,
-AIX 5.1, SunOS 4.1.
 .SH BUGS
 Before Linux 2.6.21,
 .BR mincore ()
Signature · 1 line
2.53.0.1
Signature · 1 line
<https://www.alejandro-colomar.es>
#29 lore raw
In reply to Seth McDonald
Quoted 1 line · Seth McDonald

Hi Alex,

Hi Seth,

Quoted 3 lines

Apologies on my end also for my delayed response. I've made some large but hopefully beneficial changes to my email workflow – as can be seen with the different email address.

:)

Quoted 6 lines
Quoted 2 lines

This patch seems to be corrupt. [...] Probably another issue with protonmail, I guess.

Yeah at this point I give up with ProtonMail. I shouldn't have to fix all their issues for them just to send in a patch. Hopefully Fastmail serves me better.

So far it works. I could apply the patch.

I personally use Migadu <https://migadu.com/>. I've had a very good experience with them, and they're very quick in fixing any bugs I report to them. If Fastmail works fine for you, that's great!

Quoted 6 lines

Anyhow, this is just the patch for mincore(2) with a few minor adjustments on the commit message. I won't PGP sign it yet as I first want to ensure everything works before adding things on top. But if all is well, I'll continue to sign my patches with my more secure key:

E9D1 26A5 F0D4 9DF7 792B C2E2 B4BF 4530 D39B 2D51

Ok.

BTW, the ubuntu keyserver shows the existence of a non-revoked key that is probably old?

	pub (4)eddsa263/82b9620e53d0a1ae2d696111c267b0020a900289 2024-12-06T06:53:33Z

It contains two UIDs, one of which is revoked, but the other is not revoked:

	uid [email protected] <[email protected]>
	sig cert  c267b0020a900289 2024-12-06T06:53:33Z ____________________ ____________________ [selfsig]

	uid Seth McDonald (email encryption) <[email protected]>
	sig revok c267b0020a900289 2026-02-11T08:27:33Z ____________________ ____________________ [selfsig]

Is it intentionaly that you revoked the UID instead of the key? If you want to revoke the entire key, you should probably use gpg(1)'s --gen-revoke flag, which generates a revocation certificate for the master key.

Quoted 3 lines

Let me know if it's still corrupt, and I'll ̶k̶i̶c̶k̶ ̶m̶y̶ ̶P̶C calmly figure out what's going on.

It worked. :)

Cheers,
Alex

Quoted 63 lines

Seth McDonald (1):
man/man2/mincore.2: HISTORY: Update appearances of mincore(2)

 man/man2/mincore.2 | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

Range-diff against v1:

 1:  d109f3dc06e2 <  -:  ------------ man/man2/ioctl_eventpoll.2: HISTORY: ffix
 2:  55de16b213bf <  -:  ------------ man/man2/kill.2: HISTORY: Update POSIX appearances of kill(2)
 3:  17eacf0f2d3e <  -:  ------------ man/man2/link.2: HISTORY: Change order of linkat(2)
 4:  bec317b8ee88 <  -:  ------------ man/man2/link.2: HISTORY: Update POSIX appearances of link(2)
 5:  2024c82a058d <  -:  ------------ man/man2/listen.2: HISTORY: Change order
 6:  bcf9f5113f3c <  -:  ------------ man/man2/lseek.2: HISTORY: Update appearances of SEEK_{DATA,HOLE}
 7:  2dd12d136bf0 <  -:  ------------ man/man2/lseek.2: HISTORY: Update POSIX appearances of lseek(2)
 8:  817af323707e !  1:  b1b6f011a7d3 man/man2/mincore.2: HISTORY: Update appearances of mincore(2)

@@ Metadata
## Commit message ##
man/man2/mincore.2: HISTORY: Update appearances of mincore(2)

- mincore(2) was implemented in FreeBSD on 1995-10-21,[1] which was first
+ mincore(2) was implemented in FreeBSD on 1995-10-21,[1] and was first
included in the FreeBSD 2.2 release on 1997-03.[2]

- It was implemented in NetBSD on 1999-06-15,[3] which was first included
- in the NetBSD 1.5 release on 2000-12-06,[4] (despite the commit message
+ It was implemented in NetBSD on 1999-06-15,[3] and was first included in
+ the NetBSD 1.5 release on 2000-12-06,[4] (despite the commit message
stating its intended inclusion in NetBSD 1.4.1).

- It was implemented in OpenBSD on 2001-03-09,[5] which was first included
+ It was implemented in OpenBSD on 2001-03-09,[5] and was first included
in the OpenBSD 2.9 release on 2001-06-01.[6]

All other listed systems are taken at face value and rearranged in chronological-ish order.

[1] Dyson, John (21 Oct 1995). "Implement mincore system call."
- FreeBSD source tree (Git repository).
- <https://cgit.freebsd.org/src/commit/?id=02c04a2f6c83ee28ed637d120296d04da8f03372>
+ FreeBSD source tree (Git repository). Commit
+ 02c04a2f6c83ee28ed637d120296d04da8f03372.
[2] The FreeBSD Project (29 Nov 2025). "Prior Releases – EOL".
<https://www.freebsd.org/releases>
[3] Thorpe, Jason (15 Jun 1999). "Several changes, developed and tested

 9:  8b25a256e60f <  -:  ------------ man/man2/mkdir.2: HISTORY: Change order of mkdirat(2)
10:  347e36c11666 <  -:  ------------ man/man2/mkdir.2: HISTORY: Update BSD and POSIX appearances of mkdir(2)
11:  d3da8260e1bc <  -:  ------------ man/man2/mknod.2: HISTORY: Change order of mknodat(2)
12:  b0feda20f21d <  -:  ------------ man/man2/mknod.2: HISTORY: Update POSIX appearances of mknod(2)
13:  32bd25fd3630 <  -:  ------------ man/man2/mknod.2: STANDARDS: Update
14:  67bf0c1aa133 <  -:  ------------ man/man2/mlock.2: HISTORY: Update POSIX appearances of m(un)lock(all)(2)
15:  57292b4f60c4 <  -:  ------------ man/man2/mmap.2: HISTORY: Update POSIX appearances of m(un)map(2)
16:  b8f4e6fa54e7 <  -:  ------------ man/man2/{mount_setattr,move_mount}.2: HISTORY: ffix
17:  4e1acc0f5e00 <  -:  ------------ man/man2/mprotect.2: HISTORY: Update POSIX appearances of mprotect(2)
18:  024ce32c9da5 <  -:  ------------ man/man2/msgctl.2: STANDARDS, HISTORY: Update POSIX appearances of msgctl(2)
19:  975e61bea29f <  -:  ------------ man/man2/msgget.2: STANDARDS, HISTORY: Update POSIX appearances of msgget(2)
20:  86e7c24b1428 <  -:  ------------ man/man2/msgop.2: STANDARDS, HISTORY: Update POSIX appearances of msg{rcv,snd}(2)
21:  d106bca86ec1 <  -:  ------------ man/man2/msync.2: HISTORY: Update POSIX appearances of msync(2)

base-commit: e2cc229b7551a63bb51853c849ce1a9e95946637

Signature · 1 line
2.53.0.1
Signature · 1 line
<https://www.alejandro-colomar.es>
#30 lore raw

Hi Alex,

Quoted 3 lines · Alejandro Colomar

I personally use Migadu <https://migadu.com/>. I've had a very good experience with them, and they're very quick in fixing any bugs I report to them. If Fastmail works fine for you, that's great!

I'm actually quite surprised I didn't come across them. I tried looking at every email provider (even considered Purelymail, which I believe is currently a 2-3 person project). Migadu do look great from their website, so I'll keep them in mind as a good backup.

Quoted 7 lines

BTW, the ubuntu keyserver shows the existence of a non-revoked key that is probably old?

	pub (4)eddsa263/82b9620e53d0a1ae2d696111c267b0020a900289 2024-12-06T06:53:33Z

It contains two UIDs, one of which is revoked, but the other is not revoked:

[...]

Quoted 1 line

Is it intentionaly that you revoked the UID instead of the key?

That actually was intentional. The two signatures on my key are of the keys I used with my Proton emails; I signed it to show that I'm indeed the same person despite the different email address.

I added the second UID to imply that of the two keys, if someone wanted to send me encrypted email, they should use the one whose UID states "email encryption". But since I'm no longer planning on those being my main email addresses, I revoked the "email encryption" UID. But my Proton address does still use that key, so I didn't revoke the whole thing.

Quoted 4 lines
Quoted 2 lines

Let me know if it's still corrupt, and I'll ̶k̶i̶c̶k̶ ̶m̶y̶ ̶P̶C calmly figure out what's going on.

It worked. :)

Well that's certainly a relief!

Btw, did the strikethrough text render correctly for you? It renders as strikethrough for me on mutt(1) and vim(1), but it looks -l-i-k-e- -t-h-i-s on the lore.kernel.org archive.

Take care,
Seth McDonald.

Signature · 1 line
E9D1 26A5 F0D4 9DF7 792B  C2E2 B4BF 4530 D39B 2D51
#31 lore raw

Hi Seth,

Quoted 26 lines · Seth McDonald

Hi Alex,

Quoted 3 lines · Alejandro Colomar

I personally use Migadu <https://migadu.com/>. I've had a very good experience with them, and they're very quick in fixing any bugs I report to them. If Fastmail works fine for you, that's great!

I'm actually quite surprised I didn't come across them. I tried looking at every email provider (even considered Purelymail, which I believe is currently a 2-3 person project). Migadu do look great from their website, so I'll keep them in mind as a good backup.

Quoted 7 lines

BTW, the ubuntu keyserver shows the existence of a non-revoked key that is probably old?

	pub (4)eddsa263/82b9620e53d0a1ae2d696111c267b0020a900289 2024-12-06T06:53:33Z

It contains two UIDs, one of which is revoked, but the other is not revoked:

[...]

Quoted 1 line

Is it intentionaly that you revoked the UID instead of the key?

That actually was intentional. The two signatures on my key are of the keys I used with my Proton emails; I signed it to show that I'm indeed the same person despite the different email address.

Quoted 6 lines

I added the second UID to imply that of the two keys, if someone wanted to send me encrypted email, they should use the one whose UID states "email encryption". But since I'm no longer planning on those being my main email addresses, I revoked the "email encryption" UID. But my Proton address does still use that key, so I didn't revoke the whole thing.

Ahh, makes sense.

Quoted 9 lines
Quoted 5 lines
Quoted 3 lines

Let me know if it's still corrupt, and I'll ̶k̶i̶c̶k̶ ̶m̶y̶ ̶P̶C calmly figure out what's going on.

It worked. :)

Well that's certainly a relief!

Btw, did the strikethrough text render correctly for you?

Yup, it looks correct on mutt(1) and neomutt(1).

Have a lovely day!
Alex

Quoted 9 lines

It renders as
strikethrough for me on mutt(1) and vim(1), but it looks -l-i-k-e- -t-h-i-s on the lore.kernel.org archive.

Take care,
Seth McDonald.

Signature · 1 line
E9D1 26A5 F0D4 9DF7 792B  C2E2 B4BF 4530 D39B 2D51
Signature · 1 line
<https://www.alejandro-colomar.es>