From: Alejandro Colomar <alx@kernel.org>
To: enh <enh@google.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: _Fork()
Date: Thu, 29 Feb 2024 23:49:21 +0100 [thread overview]
Message-ID: <ZeEJ8QeRhVRDs4Mv@debian> (raw)
In-Reply-To: <CAJgzZopUo5eHBBqJBnsw9AnuDVypzf7GM9vyK5a-btqsZ6Sevg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 638 bytes --]
Hi Elliott,
On Thu, Feb 29, 2024 at 02:12:12PM -0800, enh wrote:
> (apologies for the post without a patch but...)
No worries. :)
> fyi, i noticed that there's no reference to _Fork() anywhere. i'd send
> a patch, but given that vfork() has a page to itself, i'm assuming
> just adding a paragraph to fork(2) isn't the plan?
Hmmm, I didn't know about the existence of _Fork(). It looks like
_Exit(3) and exit(3), right? Maybe we could write a page based on
_Exit(3). What do you think?
Have a lovely night!
Alex
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-29 22:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 22:12 _Fork() enh
2024-02-29 22:49 ` Alejandro Colomar [this message]
2024-02-29 23:14 ` _Fork() enh
2025-05-24 18:46 ` _Fork() Alejandro Colomar
2025-05-27 13:48 ` _Fork() enh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZeEJ8QeRhVRDs4Mv@debian \
--to=alx@kernel.org \
--cc=enh@google.com \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).