On 04/04/2014 06:14 AM, Tom H wrote:
> On Fri, Apr 4, 2014 at 7:10 AM, David Sommerseth
> <[log in to unmask]> wrote:
>>
>> Bind mounts are "special". It basically mounts an already mounted
>> directory yet another place. Say you have this scheme:
>>
>> /dev/sda4 -> /mnt/mydata
>> /dev/sdb2 -> /mnt/friendsdata
>>
>> If you add a 'friends' directory in /mnt/mydata ... giving you
>> /mnt/mydata/friends, and the do bind mount:
>>
>> mount -o bind /mnt/friendsdata /mnt/mydata/friends
>>
>> This results in that you have access to the same data in both
>> /mnt/friendsdata and /mnt/mydata/friends ... But all data is read and
>> written from/to /dev/sdb2. It's just that you have "loaned" an already
>> mounted directory into your /mnt/mydata directory.
>>
>> These bind mounts are kind of a "I want what you have"-mount.
>>
>> Bind mounts are particularly handy when you work with chroots and wants
>> to grant access to certain files outside the chroot, where symlink is
>> impossible. With bind mounts, you can also the same with files; not
>> just directories.
>
> For the sake of completeness - and also in anticipation of SL7's
> symlinking of "/etc/mtab" to "/proc/self/mounts":
>
> http://karelzak.blogspot.ch/2011/04/bind-mounts-mtab-and-read-only.html
>

Hi Tom and David,

    Thank you!

-T

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~