From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] name space question
Date: Thu, 29 Sep 2005 14:12:45 -0400 [thread overview]
Message-ID: <ee9e417a0509291112t607f88bcl980281ad37cccf4c@mail.gmail.com> (raw)
In-Reply-To: <Pine.GSO.4.61.0509291352350.7525@cps210.cps.cmich.edu.>
> Say a process is created with rofrk flag RFCNAMEG
> -- clean name space. A little confusion here: does
> it mean that search path defaults (before rfork) are
> now lost.
The search path (contained in the environment)
is left alone, but there is no longer a /bin!
> If so, I would like to see an example code
> for building new name space in the forked process.
See /sys/src/libauth/newns.c. The # paths are still available
and are used to get back off the ground.
Russ
prev parent reply other threads:[~2005-09-29 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 18:04 ISHWAR RATTAN
2005-09-29 18:12 ` Russ Cox [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=ee9e417a0509291112t607f88bcl980281ad37cccf4c@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
/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).