public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
* Issue in man page syscalls.2
@ 2023-11-01 14:02 Helge Kreutzmann
  2023-11-01 16:14 ` Alejandro Colomar
  0 siblings, 1 reply; 10+ messages in thread
From: Helge Kreutzmann @ 2023-11-01 14:02 UTC (permalink / raw)
  To: alx.manpages; +Cc: mario.blaettermann, linux-man

Without further ado, the following was found:

Issue:    And the Linux 6.x series?

"Starting with Linux 2.6.0, the development model changed, and new system "
"calls may appear in each Linux 2.6.x release.  In this case, the exact "
"version number where the system call appeared is shown.  This convention "
"continues with the Linux 3.x kernel series, which followed on from Linux "
"2.6.39; and the Linux 4.x kernel series, which followed on from Linux 3.19; "
"and the Linux 5.x kernel series, which followed on from Linux 4.20."

^ permalink raw reply	[flat|nested] 10+ messages in thread
* Issue in man page syscalls.2
@ 2023-11-01 14:02 Helge Kreutzmann
  2023-11-01 16:29 ` Alejandro Colomar
  0 siblings, 1 reply; 10+ messages in thread
From: Helge Kreutzmann @ 2023-11-01 14:02 UTC (permalink / raw)
  To: alx.manpages; +Cc: mario.blaettermann, linux-man

Without further ado, the following was found:

Issue:    kernel Linux → Linux

"Where a system call is marked \"2.2\" this means the system call probably "
"appeared in a Linux 2.1.x kernel version, and first appeared in a stable "
"kernel with Linux 2.2.0.  (Development of the Linux 2.2 kernel was initiated "
"from a branch of kernel Linux 2.0.21 via the Linux 2.1.x unstable kernel "
"series.)"

^ permalink raw reply	[flat|nested] 10+ messages in thread
* Issue in man page syscalls.2
@ 2024-11-17 10:46 Helge Kreutzmann
  2024-11-17 12:06 ` Alejandro Colomar
  0 siblings, 1 reply; 10+ messages in thread
From: Helge Kreutzmann @ 2024-11-17 10:46 UTC (permalink / raw)
  To: alx; +Cc: mario.blaettermann, linux-man

Without further ado, the following was found:

Issue:    Is the first one correct? In Debian, ausyscall(8) exists

"B<ausyscall>(1), B<intro>(2), B<syscall>(2), B<unimplemented>(2), "
"B<errno>(3), B<libc>(7), B<vdso>(7)"

^ permalink raw reply	[flat|nested] 10+ messages in thread
* Issue in man page syscalls.2
@ 2025-08-24 14:48 Helge Kreutzmann
  2025-09-01  8:09 ` Alejandro Colomar
  0 siblings, 1 reply; 10+ messages in thread
From: Helge Kreutzmann @ 2025-08-24 14:48 UTC (permalink / raw)
  To: alx; +Cc: mario.blaettermann, linux-man

Without further ado, the following was found:

Issue:    GID -> UID?

"returns a pair of GID and effective GID via registers B<r0> and B<r20>; it "
"is provided instead of B<getuid>(2)  and B<geteuid>(2)."

^ permalink raw reply	[flat|nested] 10+ messages in thread
* Issue in man page syscalls.2
@ 2025-08-24 14:48 Helge Kreutzmann
  2025-09-01  8:08 ` Alejandro Colomar
  0 siblings, 1 reply; 10+ messages in thread
From: Helge Kreutzmann @ 2025-08-24 14:48 UTC (permalink / raw)
  To: alx; +Cc: mario.blaettermann, linux-man

Without further ado, the following was found:

Issue:    Why these strange line breaks?

"See\n"
"B<chown>(2)\n"
"for\n"
"version details"

"Alternative name for\n"
"B<setpgid>(2)\n"
"on Alpha"

^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2025-09-01  8:10 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-11-01 14:02 Issue in man page syscalls.2 Helge Kreutzmann
2023-11-01 16:14 ` Alejandro Colomar
  -- strict thread matches above, loose matches on Subject: below --
2023-11-01 14:02 Helge Kreutzmann
2023-11-01 16:29 ` Alejandro Colomar
2024-11-17 10:46 Helge Kreutzmann
2024-11-17 12:06 ` Alejandro Colomar
2025-08-24 14:48 Helge Kreutzmann
2025-09-01  8:09 ` Alejandro Colomar
2025-08-24 14:48 Helge Kreutzmann
2025-09-01  8:08 ` Alejandro Colomar

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox