From: Gorka Guardiola Muzquiz <paurea@rabel.it.uc3m.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] union directories
Date: Thu, 22 Mar 2001 03:57:03 +0100 [thread overview]
Message-ID: <E14fvHb-0002R2-00@rabel.it.uc3m.es> (raw)
Russ> Actually that's the way it's supposed to work.
The manual says "creation goes to the first element of the union that
permits creation". Doesn't that means that it should jump over non_writeble?
Even taking that in account, I can't see the logic behind this behaviour.
Lookup should win whenever creation wins. That would be symmetrical and
clean. with bind -ac n1 n2, bind -bc n1 n2, bind -ac n2 n1, bind -bc n2 n1
you would cover all the logical possibilities, and you save doing
bind -c n1 n2
next reply other threads:[~2001-03-22 2:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 2:57 Gorka Guardiola Muzquiz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-03 20:45 Keith Nash
2003-03-03 20:51 ` Russ Cox
2003-03-03 20:00 Keith Nash
2003-03-03 20:05 ` Russ Cox
2003-03-03 18:58 rog
2003-03-03 23:17 ` anyrhine
2003-03-03 13:18 rog
2003-03-03 17:40 ` Ronald G. Minnich
2003-03-03 18:05 ` Russ Cox
2003-03-03 18:09 ` Ronald G. Minnich
2003-03-03 18:16 ` Russ Cox
2003-02-28 18:52 Joel Salomon
2003-02-28 18:56 ` Russ Cox
2003-02-28 21:16 ` Jack Johnson
2003-02-28 22:58 ` Geoff Collyer
2003-02-28 23:19 ` Jack Johnson
2003-02-28 23:59 ` Geoff Collyer
2003-02-15 19:37 [9fans] presentation preparation Scott Schwartz
2003-02-15 19:48 ` andrey mirtchovski
2003-02-27 9:35 ` Ralph Corderoy
2003-02-28 18:44 ` [9fans] union directories Jack Johnson
2003-02-28 18:53 ` Russ Cox
2003-03-04 9:44 ` Adrian Tritschler
2001-03-23 13:30 G. David Butler
2001-03-23 13:08 rog
2001-03-26 8:44 ` Douglas A. Gwyn
2001-03-22 3:28 rob pike
2001-03-23 10:06 ` Douglas A. Gwyn
2001-03-22 2:46 Gorka Guardiola Muzquiz
2001-03-22 2:42 Gorka Guardiola Muzquiz
2001-03-22 2:37 Russ Cox
2001-03-22 2:02 Russ Cox
2001-03-22 1:56 Gorka Guardiola Muzquiz
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=E14fvHb-0002R2-00@rabel.it.uc3m.es \
--to=paurea@rabel.it.uc3m.es \
--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).