From: paurea@dei.inf.uc3m.es
To: 9fans@cse.psu.edu
Subject: [9fans] strange behaviour of bind
Date: Thu, 22 Mar 2001 01:59:11 +0100 [thread overview]
Message-ID: <15033.20063.386721.676087@nido.hilbert.space> (raw)
I have encountered a behaviour in bind (well, actually in the fs) which
I find inconsistent. I may not be a bug, but it is counter intuitive.
Say you have two directories free_space and non_writable.
If you write:
bind -bc free_space non_writable
You add space to non_writable. Everything works fine. free_space is before
non_writable in non_writable. If you create a file in non_writable you
are actually creating int in free_space.
bind -ac non_writable2 free_space2
non_writable2 is after free_space2 in free_space2. You should be able to
write in free_space. *you can't*. Even stranger:
bind -ac fspace1 fspace2
Any file in fspace2 supersedes any file in fspace1 with the same name,
but if you create a file in fspace2 it is actually created *in fspace1*!!!???.
fspace1 is *after* fspace2 for already existing files,
but it is *before* when you create new ones.
I find this weird and counter intuitive. It also seems to contradict
the manual page. Is there any reason for this?. Is there something
I am not getting?.
--
Saludos,
Gorka
"Curiosity sKilled the cat"
--
/"\
\ / ascii ribbon campaign - against html mail
X - against ms attachments
/ \
reply other threads:[~2001-03-22 0:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=15033.20063.386721.676087@nido.hilbert.space \
--to=paurea@dei.inf.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).