From: "Antonin Vecera" <antonin.vecera@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] patch for /rc/bin/cpurc
Date: Thu, 19 Jul 2007 21:25:45 +0200 [thread overview]
Message-ID: <10b109140707191225y211ebbf6id4f63fccea5232fc@mail.gmail.com> (raw)
In-Reply-To: <4799c65eb8663fa87153808941ade72c@plan9.bell-labs.com>
On 7/19/07, geoff@plan9.bell-labs.com <geoff@plan9.bell-labs.com> wrote:
> listen calls newns() internally, so changing the namespace by hand
> doesn't affect it. listen can be given alternate service directories
> (see listen(8)) and will now ignore zero-length files in the service
> directories, so binding /dev/null onto files in /bin/service (for
> example) in /cfg/$sysname/namespace can be used to alter the set of
> services offered.
You are right.
Better way is to create file /cfg/$sysname/namespace .
I didn't know about this option.
Thanks.
Antonin
prev parent reply other threads:[~2007-07-19 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 8:58 Antonin
2007-07-19 15:28 ` David Leimbach
2007-07-19 17:15 ` geoff
2007-07-19 19:25 ` Antonin Vecera [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=10b109140707191225y211ebbf6id4f63fccea5232fc@mail.gmail.com \
--to=antonin.vecera@gmail.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).