* [PATCH] execve.2: point to exec(3) early
@ 2022-05-25 19:30 наб
2022-05-25 19:34 ` Alejandro Colomar
0 siblings, 1 reply; 2+ messages in thread
From: наб @ 2022-05-25 19:30 UTC (permalink / raw)
To: Alejandro Colomar (man-pages); +Cc: linux-man
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
Most people actually want exec(3) (or one of its aliases);
the minutiae are a separate, rarer, concern, and execve(2) hijacks
man execve from all the other exec(3) aliases
(similarly to exec(1posix), but it's at least obvious in that case that
you got the wrong page)
Reported-in: https://twitter.com/NireBryce/status/1529538043039850499
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
---
man2/execve.2 | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/man2/execve.2 b/man2/execve.2
index 0d9582492..28c175132 100644
--- a/man2/execve.2
+++ b/man2/execve.2
@@ -80,6 +80,14 @@ The
.I envp
array must be terminated by a NULL pointer.
.PP
+This manual page describes the Linux system call in detail;
+for an overview of the nomenclature and the many, often preferable,
+standardised variants of this function provided by libc,
+including ones that search the
+.B PATH
+environment variable, see
+.BR exec (3).
+.PP
The argument vector and environment can be accessed by the
new program's main function, when it is defined as:
.PP
--
2.30.2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] execve.2: point to exec(3) early
2022-05-25 19:30 [PATCH] execve.2: point to exec(3) early наб
@ 2022-05-25 19:34 ` Alejandro Colomar
0 siblings, 0 replies; 2+ messages in thread
From: Alejandro Colomar @ 2022-05-25 19:34 UTC (permalink / raw)
To: наб; +Cc: linux-man
[-- Attachment #1.1: Type: text/plain, Size: 1321 bytes --]
Hi наб!
On 5/25/22 21:30, наб wrote:
> Most people actually want exec(3) (or one of its aliases);
> the minutiae are a separate, rarer, concern, and execve(2) hijacks
> man execve from all the other exec(3) aliases
> (similarly to exec(1posix), but it's at least obvious in that case that
> you got the wrong page)
>
> Reported-in: https://twitter.com/NireBryce/status/1529538043039850499
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Patch applied.
Thanks!
Alex
> ---
> man2/execve.2 | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/man2/execve.2 b/man2/execve.2
> index 0d9582492..28c175132 100644
> --- a/man2/execve.2
> +++ b/man2/execve.2
> @@ -80,6 +80,14 @@ The
> .I envp
> array must be terminated by a NULL pointer.
> .PP
> +This manual page describes the Linux system call in detail;
> +for an overview of the nomenclature and the many, often preferable,
> +standardised variants of this function provided by libc,
> +including ones that search the
> +.B PATH
> +environment variable, see
> +.BR exec (3).
> +.PP
> The argument vector and environment can be accessed by the
> new program's main function, when it is defined as:
> .PP
--
Alejandro Colomar
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-05-25 19:35 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-05-25 19:30 [PATCH] execve.2: point to exec(3) early наб
2022-05-25 19:34 ` Alejandro Colomar
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox