From: Russ Cox <russcox@gmail.com>
To: Sergey Reva <rs_rlab@mail.ru>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] couple namespace question
Date: Sat, 7 May 2005 08:56:09 -0400 [thread overview]
Message-ID: <ee9e417a050507055678ad5563@mail.gmail.com> (raw)
In-Reply-To: <1635217046.20050507114444@mail.ru>
> Why most process have 'ns' file with entryes:
> bind / /
> bind /net /net
> bind /n /n
> This is artifactes or some special functionality?
This sets up the first entry of a union mount.
In older versions you couldn't bind -a or -b
until you had explicitly started a mount point
using something like the above, but now the
kernel does them for you when necessary.
> Where is sane way to use proc fs:
> '#p/34/ctl' or '/proc/34/ctl'
Almost always use /proc. If you use #p then the tool
does not play well with others like snapfs or
import remote-machine /proc.
Russ
prev parent reply other threads:[~2005-05-07 12:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-07 8:44 Sergey Reva
2005-05-07 12:56 ` 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=ee9e417a050507055678ad5563@mail.gmail.com \
--to=russcox@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=rs_rlab@mail.ru \
/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).