Re: [9fans] bind -c[ab] -- what am I doing wrong?

[northern snowfall <dbailey27@ameritech.net>]

>
>
>who's to blame?
>
You are! Binds make a list of directories like a linked
list chain. Our operations on these directories can always
be considered one of two primaries: read or write. Respectively,
we can think as the first link in the chain as the link we
Read from:
    cpu% cd
    cpu% mkdir testme
    cpu% cat > testme/u.h << EOF
        hello!
        EOF
    cpu% bind -bc testme /386/include
    cpu% wc -l /386/include/u.h
          1 /386/include/u.h
    cpu% cat /386/include/u.h
    hello!
    cpu% unmount /386/include

Or, we Read from the first bound directory that contains the
file we've requested access to. So, if 'testme' didn't contain
an u.h, the Read would return /386/include/u.h, despite testme
being bound 'before' /386/include/u.h.

Writes always take effect in the first directory we have permission
to write to in the chain. Most often this is the last link in the
chain:
    cpu% bind -ac testme /386/include/
    cpu% touch /386/include/foo
    cpu% ls -l testme/foo
    --rw-rw-r-- M 2265 snowfall snowfall 0 Jul 17 11:35 testme/foo
    cpu% unmount /386/include
    cpu%

So, if multiple directories we can write to were bound 'after'
our primary unwritable, we write to the first:
    cpu% bind -ac /tmp /386/include
    cpu% bind -ac testme /386/include
    cpu% touch /386/include/foo2
    cpu% ls -l /tmp/foo2
    --rw-rw-r-- M 2265 snowfall snowfall 0 Jul 17 11:38 /tmp/foo2
    cpu%

Hope that helps!
Don

http://www.7f.no-ip.com/~north_







>