From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Message-Id: From: Gorka Guardiola Muzquiz Subject: [9fans] union directories Date: Thu, 22 Mar 2001 02:56:48 +0100 Topicbox-Message-UUID: 72511c4e-eac9-11e9-9e20-41e7f4b1d025 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 / \