9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] newns
Date: Fri, 10 Nov 2000 08:50:59 +0000	[thread overview]
Message-ID: <E13u9tk-0005un-0C@finch-post-12.mail.demon.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 132 bytes --]

Yes, I'd noticed that. The ftp namespace is similar as well.
If you don't have /usr/web then anonymous users see
_everything_.


[-- Attachment #2: Type: message/rfc822, Size: 1846 bytes --]

From: arisawa@ar.aichi-u.ac.jp
To: 9fans@cse.psu.edu
Subject: [9fans] newns
Date: Fri, 10 Nov 2000 17:28:34 0900
Message-ID: <20001110082938.9949D199E4@mail.cse.psu.edu>

Hello,

I have a question on the system library function "newns":
newns does not inform the line in /lib/namespace*
when it failed in building namespace.
That is, function "nsop" in newns.c does not check the result status
of the functions bind, mount, ... etc.
Are there anything wrong if newns returns when
it failed in executing these commands and report the problem ?

P.S.
I thought of that, because httpd does not work on my cpu server
with 9pccpudisk.
httpd fails at:
becomenone(char *namespace)
{	...
	if(newns("none", nil) < 0)
		sysfatal("can't build normal namespace: %r");
	...
}
of httpd.c, and the problem comes from:
mount -a /srv/net /net
in /lib/namespace

Of course I added a patch to newns to report the problem.

Kenji Arisawa
E-mail: arisawa@aichi-u.ac.jp

             reply	other threads:[~2000-11-10  8:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-10  8:50 nigel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-11-10  8:28 arisawa

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=E13u9tk-0005un-0C@finch-post-12.mail.demon.net \
    --to=nigel@9fs.org \
    --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).