9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] hack for /usr/$user/lib/face
Date: Tue,  2 Sep 2003 19:00:46 -0700	[thread overview]
Message-ID: <c0cb47882d66112b2a68a6bdd1fbd378@collyer.net> (raw)
In-Reply-To: <9c093fad03d6d5f4270a7c0558de7193@granite.cias.osakafu-u.ac.jp>

ovfs was originally meant to allow overlaying of the contents of one
file server's main file system onto another one, but I can see plenty
of other uses for it.

I and everybody I've talked to about this says `Yeah, when I first
heard about Plan 9's binds, I assumed that they were recursive', thus
letting a user customise the system easily and extensively with
something like

	bind -b /usr/$user /

Maybe we're all dolts, but I think that something about the way binds
are explained sets people's expectations to be at odds with the
reality of bind's implementation.  Or maybe we just extrapolate what
appears to be an obvious extension (though of course it isn't, given
the implementation).



  reply	other threads:[~2003-09-03  2:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-02  3:55 matt
2003-09-02  6:44 ` okamoto
2003-09-02 14:16   ` Russ Cox
2003-09-02 14:48   ` boyd, rounin
2003-09-02 14:54     ` David Presotto
2003-09-02 15:04       ` andrey mirtchovski
2003-09-02 15:04       ` boyd, rounin
2003-09-02 17:05       ` Russ Cox
2003-09-02 22:15         ` david presotto
2003-09-03  2:00           ` Dan Cross
2003-09-03  7:15             ` Fco.J.Ballesteros
2003-09-02 21:33       ` Geoff Collyer
2003-09-03  1:07         ` okamoto
2003-09-03  2:00           ` Geoff Collyer [this message]
2003-09-03  2:29             ` okamoto
2003-09-03  2:33               ` Geoff Collyer
2003-09-03  2:38                 ` okamoto
2003-09-02 19:49 matt
2003-09-02 19:50 matt
2003-09-02 19:57 matt

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=c0cb47882d66112b2a68a6bdd1fbd378@collyer.net \
    --to=geoff@collyer.net \
    --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).