On Friday, 18 November 2016 17:16:53 UTC, Prototype wrote:
Thank you for explanation.
Ah, now you can start writing the docs :-)
Yes, but in that example, as no packages with initscripts were yet installed, one didn't know if /Alt-F/etc/init.d/ or even /Alt-F/etc/ exists, so I took the direct approach. Generally that is not needed, try first the normal course of action and if it does not reflects under Alt-F use the lengthy approach. Once it works the first time it is not needed a second time.
Yes, as my command line example in the previous post shows. But only if the parent dir exists. In your example, /etc/some/thing, as folder '/etc/some' does not exists, you have to create if first, 'mkdir /etc/some', and as '/Alt-F/etc' exists, the 'some' folder will be created under it; then as as you create file 'thing', it will also also appear under /Alt-F/etc/some.
All the above is only possible after the Alt-F folder is first discovered in the base of a filesystem. You can check that by using 'aufs.sh -l', which should display all the aufs layers, top priority on top, being it /mnt/whatever/Alt-F.
But (there are many buts and ifs in this matter), when the Alt-F folder is discovered and put on top of the aufs layer, the current box settings loaded from flash memory (and only those) will be copied to the Alt-F folder, overwriting the ones existing there. And the reverse occurs at power-down or when the Alt-F folder filesystem is unmounted ('aufs.sh -u' does that *if* possible).
This is needed to maintain settings consistency -- the box "identity" is stored on flash memory and not on disk, as disks are (was, in the previous box hardware design) easily swappable.