From: Tom <tom.lobato@terra.com.br>
To: linux-c-programming@vger.kernel.org
Subject: fork: why to copy process to run new program?
Date: Sun, 03 Jul 2005 22:09:14 -0300 [thread overview]
Message-ID: <daa27s$1kr$1@sea.gmane.org> (raw)
Hello!
Why, when a program needs to open another, have fork to copy all the
initial program just for 'exec' the another? Could'nt initial program just
to "tell" the kernel for open the second program?
Thank you
Tom
next reply other threads:[~2005-07-04 1:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-04 1:09 Tom [this message]
2005-07-04 2:01 ` fork: why to copy process to run new program? Ron Michael Khu
2005-07-04 2:14 ` Glynn Clements
2005-07-04 11:46 ` Tom
2005-07-04 12:09 ` Steve Graegert
2005-07-04 14:51 ` Glynn Clements
2005-07-05 3:00 ` Ron Michael Khu
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='daa27s$1kr$1@sea.gmane.org' \
--to=tom.lobato@terra.com.br \
--cc=linux-c-programming@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).