9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: frank@inua.be
To: 9fans@9fans.net
Subject: Re: [9fans] playing with namespaces
Date: Mon, 27 Sep 2010 22:33:14 +0200	[thread overview]
Message-ID: <20100927203314.GA12249@chiron.galaxy> (raw)
In-Reply-To: <076604d7e2a8417033c7a50f4e7638c2@plug.quanstro.net>

On Sun, Sep 26, 2010 at 05:41:24PM -0400, erik quanstrom wrote:
> > - I copied /rc/bin/service.auth to /cfg/<authhost>/slash and enabled
> >   tcp567 and then added a bind -b of that directory to the original
> >   /rc/bin/service.auth.
>
> the traditional way of doing this is to create directories
> service.$function and/or service.$function.auth and use them
> as arguments to listen.  the exact arguments to listen should

I see what you mean but I wanted to avoid changing /rc/bin/cpurc so
that it could stay the way it was distributed and updated as if it was
never touched.[*]

In addition to that, I also wanted the play around with namespaces
(hence the subject of the e-mail). All in all, the traditional way of
doing this isn't that different: both have an extra directory
containing the services; in one case, listening is done using that
directory, in the other case, listening is done as usual but with an
"overlay". I have to admit however, that the traditional way of doing
it is cleaner (easier to understand, more transparant).

[*] I haven't yet looked at how pull updates the system.

> depend on $sysname (whaever your cpurc setup).  that way,
> you don't have stuff that's mucking with the namespace depending
> to much on construction of the namespace.

I agree but as I'm trying to understand the mechanisms, the questions
I had still remain:

- Why is it that, when the namespace is changed in
  /cfg/$sysname/cpurc, it does not seem to be taken into account by
  the aux/listen in /rc/bin/cpurc?

- Why can't a modified rc/bin/service.auth not be bound via
  /cfg/$sysname/namespace?

Has it something to do with user none versus user bootes or so?

> - erik

--
Frank Lenaerts ---------------------------------------- frank@inua.be




  reply	other threads:[~2010-09-27 20:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-26 21:21 frank
2010-09-26 21:41 ` erik quanstrom
2010-09-27 20:33   ` frank [this message]
2010-09-27 22:16     ` erik quanstrom
2010-09-28 21:00       ` frank

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=20100927203314.GA12249@chiron.galaxy \
    --to=frank@inua.be \
    --cc=9fans@9fans.net \
    /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).