9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] tip o' the day
Date: Tue, 15 Feb 2005 17:21:58 +0000	[thread overview]
Message-ID: <8fd9ce77c40c8069aef69fa88b7d9841@vitanuova.com> (raw)
In-Reply-To: <f534ec278dee9a77f20b6107e8c1c337@crn.mteege.de>

> Yes.  I copy mntgen from source and I can see my files ;-) But if I
> run "local 9fs unixbox" first and then "local bind -c
> /n/unixbox/foo/bar /n/bar" works.

yes, that'll work because the namespace is being changed locally
to mntgen.

your previous example was failing to work because the mount was in
your current namespace - through the exportfs "window".  the mount
worked ok, but exportfs didn't keep the reference to the mount-point
around, so mntgen removed the new directory.

the next time the mount point was created by mntgen, it was given a
new qid, and since the kernel uses qids to index its mount table, it
wasn't finding your mount point.

the change i made to mntgen was always to generate the same qid for a
given name; hence although mntgen does delete the name, at least
anything mounted on it will still be visible when it's created again.

the real fix (i think) is to allow fds to refer to non-open files in
the plan 9 syscall interface (hence allowing exportfs to retain
a reference to walked-to directories without opening them),
but that's a significant change, hence unlikely to happen.

i'm sure you didn't want to know that!

  cheers,
    rog.



  reply	other threads:[~2005-02-15 17:21 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08  8:05 Russ Cox
2005-02-08  8:07 ` [9fans] " Russ Cox
2005-02-08  8:16 ` [9fans] " Tim Newsham
2005-02-08  9:41 ` Fco. J. Ballesteros
2005-02-08  9:58   ` Steve Simon
2005-02-08 12:08   ` Robert Raschke
2005-02-08  9:51 ` Steve Simon
2005-02-08 16:31   ` Ronald G. Minnich
2005-02-08 10:01 ` Catalin(ux aka Dino) BOIE
2005-02-08 11:01   ` Charles Forsyth
2005-02-08 11:04     ` Catalin(ux aka Dino) BOIE
2005-02-08 15:46 ` andrey mirtchovski
2005-02-08 16:29 ` Ronald G. Minnich
2005-02-08 17:31 ` Sam
2005-02-08 18:22   ` Heiko Dudzus
2005-02-08 19:13 ` Micah Stetson
2005-02-08 19:37   ` rog
2005-02-08 19:54     ` andrey mirtchovski
2005-02-09 16:29       ` Ronald G. Minnich
2005-02-15 14:11     ` Matthias Teege
2005-02-15 15:29       ` rog
2005-02-15 16:57         ` Matthias Teege
2005-02-15 17:21           ` rog [this message]
2005-02-15 17:26             ` Ronald G. Minnich
2005-02-15 17:34               ` rog
2005-02-16 19:17   ` McLone
2005-02-10  7:21 ` Vincent van Gelderen
2005-02-10  7:40   ` Tim Newsham
2005-02-10 14:59     ` Russ Cox
2005-02-10 19:16       ` Tim Newsham
2005-02-15 15:33 ` andrey mirtchovski
2005-02-15 16:48   ` Russ Cox
     [not found] <ee9e417a0502170724abbfaa7@mail.gmail.com>
     [not found] ` <0345be3b46120cbf06bdff45601d5540@plan9.ucalgary.ca>
     [not found]   ` <ee9e417a05021707521732ce1c@mail.gmail.com>
     [not found]     ` <Pine.LNX.4.60.0502171110160.11590@fbsd.cpsc.ucalgary.ca>
     [not found]       ` <ee9e417a050217104148427143@mail.gmail.com>
2005-02-17 18:43         ` Russ Cox
2005-02-18 16:37           ` Sergey Reva
2005-02-22 10:12 Steve Simon
2005-02-23  0:45 YAMANASHI Takeshi

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=8fd9ce77c40c8069aef69fa88b7d9841@vitanuova.com \
    --to=rog@vitanuova.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).