From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Russ Cox <rsc@swtch.com>
Subject: Re: [9fans] p9p procrfork
Date: Sat, 7 Jan 2006 20:24:12 -0600 [thread overview]
Message-ID: <20060108022412.8239A1F6C94@dexter-peak.quanstro.net> (raw)
In-Reply-To: <ee9e417a0601071710v37714f35he1a439744cf5ef2d@mail.gmail.com>
all the worlds a vax, i mean, a linux box. ;-)
i misread the source. i was reading Linux.c;
i didn't realize that that is only for nptl.
actually, i was thinking about ndb/dns is doing.
- erik
Russ Cox <rsc@swtch.com> writes
|
| > what is the reason that p9p doesn't support procrfork?
| > linux might be able to support procrfork via clone(2), but
| > of course, pthreads might have something else to say about
| > that.
|
| you answered the question yourself.
| we're not programming to linux.
| we're programming to what we can do
| portably across a range of unixes.
| file descriptor and name space groups
| (the only things you ever use procrfork for)
| are not part of that.
|
| if you need procrfork for rffdg before procexec, usually
| you can get by with threadexec etc.
|
| russ
prev parent reply other threads:[~2006-01-08 2:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-08 1:05 erik quanstrom
2006-01-08 1:10 ` Russ Cox
2006-01-08 2:24 ` erik quanstrom [this message]
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=20060108022412.8239A1F6C94@dexter-peak.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
--cc=rsc@swtch.com \
/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).