9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] sanity check
Date: Sat, 24 Sep 2005 07:28:13 -0400	[thread overview]
Message-ID: <ee9e417a050924042855691d28@mail.gmail.com> (raw)
In-Reply-To: <57a0f1f23556a07062df16b935615739@quintile.net>

10-50 extra binds won't be noticed at all as far as
performance goes.  Unfortunately for you, they also
won't be noticed at all as far as rio goes.

If you create a rio window and then you change
the name space sitting under rio, the existing window's
name space (which has already been copied from rio)
doesn't inherit the new path.  So just re-binding things
doesn't work as you might hope.

This sort of thing comes up enough that I think it
would be nice if it did work (some new flag to rfork),
but it's not there now.

One quick and dirty option is to have cifs echo the
necessary bind commands to standard output (hopefully
cifs dissociates from the name space in which it is mounted)
and run something like:

  cifs | rc; srvfs dfs /n/cifs
  mount /srv/dfs /n/dfs

Then you will see the changes under /n/dfs because of the
extra exportfs (inside srvfs) mount combination.

Russ


  reply	other threads:[~2005-09-24 11:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-24 10:22 Steve Simon
2005-09-24 11:28 ` Russ Cox [this message]
2005-09-25  3:47   ` Dave Eckhardt
2005-09-26  9:07   ` Steve Simon
2005-09-26 17:16     ` rog
2005-09-26 17:21       ` Federico Benavento
2005-09-24 14:33 Fco. J. Ballesteros
2005-09-26  9:17 ` Steve Simon

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=ee9e417a050924042855691d28@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).