You are not logged in.
- Topics: Active | Unanswered
#1 2018-11-21 23:37:26
- regid
- Member
- Registered: 2016-06-06
- Posts: 83
mount --bind /tmp/root.x86_64 /tmp/root.x86_64
mount --bind /tmp/root.x86_64 /tmp/root.x86_64 is copied from Install_from_existing_Linux#Method_A:_Using_the_bootstrap_image_(recommended).
Why would one want to bind mount a directory over itself?
I suspect the benefits are the side effects, perhaps somethings to do with namespaces. In any case, can you elaborate?
Offline
#3 2018-11-22 11:28:47
- WorMzy
- Forum Moderator
- From: Scotland
- Registered: 2010-06-16
- Posts: 8,407
- Website
Re: mount --bind /tmp/root.x86_64 /tmp/root.x86_64
Bizarrely, this has just been covered here: https://bbs.archlinux.org/viewtopic.php?id=242143
Sakura:-
Mobo: MSI X299 TOMAHAWK ARCTIC // Processor: Intel Core i7-7820X 3.6GHz // GFX: nVidia GeForce GTX 970 // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 5x 1TB HDD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
#4 2018-11-22 16:07:54
- regid
- Member
- Registered: 2016-06-06
- Posts: 83
Re: mount --bind /tmp/root.x86_64 /tmp/root.x86_64
I thank WorMzy for pointing out that other thread.
I have tried to continue this thread at that other thread. That thread partially, or perhaps fully, answers my question. WorMzy considered my attempt as hijacking, and closed it. I think he is wrong. I think wondering about the benefits of bind mounting a directory over itself is an interesting question, and to the point in that other thread too.
If someone can explain the advantages, and disadvantageous, of such a bind mount, please do so.
Last edited by regid (2018-11-22 16:09:02)
Offline