9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com rog@vitanuova.com
Subject: [9fans] spawn() vs fork()
Date: Mon,  5 Jul 1999 10:09:49 +0100	[thread overview]
Message-ID: <19990705090949.8P0iALZEDFaoKTJ25zkWEoCma3DaOGV_u9TQJ3PFH5E@z> (raw)

> Implementation requirements aside, as Jean says, fork gives you an
> elegant way of setting up I/O redirection. It also gives you an elegant
> way of determining start-up context as a whole for the new process.,
> including internal state.

inferno seems to do fine with a spawn primitive and no process
fork. it has the capability to fork resources (i.e. fds, namespace,
process group) and this, combined with the fact that there are
relatively few attributes associated with a process, seems quite
sufficient for all the usual process setup.

  cheers,
    rog.




             reply	other threads:[~1999-07-05  9:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-05  9:09 rog [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-07-05 13:23 Digby
1999-07-05  7:57 steve.kilbane
1999-07-03 15:22 Digby
1999-07-03 10:23 Jean
1999-07-03  9:53 Guan

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=19990705090949.8P0iALZEDFaoKTJ25zkWEoCma3DaOGV_u9TQJ3PFH5E@z \
    --to=rog@vitanuova.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).