You are not logged in.
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?
pantum-p1000-p2000-p3000-m5100-m5200-ppd-driver (AUR): PPDs, drivers, for Pantum P1000, P2000, P3000, M5100, M5200 printers.
powerofforreboot.efi (AUR): Utilities to be used from within a UEFI boot manager or shell.
Offline
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: AMD Radeon RX 5700 XT // 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.
Online
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)
pantum-p1000-p2000-p3000-m5100-m5200-ppd-driver (AUR): PPDs, drivers, for Pantum P1000, P2000, P3000, M5100, M5200 printers.
powerofforreboot.efi (AUR): Utilities to be used from within a UEFI boot manager or shell.
Offline