Every image is a discreet image….. and you can have eMMC images and images in an attached usb device.I'd like to know the logic of the MB (compared to the old PMB which created subfolders under the omb root).
Here we have, in the /boot/ folder, the ones named
linuxrootfs1, and so on.
but there is also the usual structure in the root folder.
Now the question is. If I need to add something manually to the image, let's say a script, when I added it in
it was added also in
but when I deleted it from /usr/script it wasn't from /boot/linuxrootfs1/usr/script.
Other strange things happened with binary in /usr/bin or camscripts in /usr/camscripts).
What is the best way to manually add files? It's always better to forget about the MB subfolders and pretending to work with the usual ones because every actions will be automatically "reproduced" in the subfolder containing the current (active) image?.
Thanks and regards.
Put the file in the active image.But you haven't answered my question. I perfectly know how settings backup works but I'm used to have full control of my images.
Getting sticked to my example, where it's better to transfer a user script file, in /usr/script/ or in /boot/linuxrootfs1/usr/script?
Incidentally, not only the images in eMMc are displayed in those folders but also the usb slots ones which are in
The reason of my post is that I saw files reappering immediately after being deleted and I need to know how to take full control of the image, being not just a passive user.
Reflash the box as normal and don't enable multiboothow to return to only one image in flash, without multiboot?
Why? Like any multiboot receiver, you only need flash one image, which you can then either software update or flash in place.how to return to only one image in flash, without multiboot?
just asking, to be sure. after all this is first arm multiboot in flash. thank youWhy? Like any multiboot receiver, you only need flash one image, which you can then either software update or flash in place.
After installation of OpenATV 6.4 to Slot3(eMMC) to my Duo4k box I need to enter recovery image to change the Slot(no multiboot menu).Only in usb3.0 port
tested at duo4k and solo4k .
Normally when you flash an image, it will reboot to that image slot(standard multiboot function), I think with OpenATV you can flash an image without rebooting.Would you pleas see if can allow user to use what image will boot on and use after install new image on slots
device is rebooted automatically on image just installed
Thanks to all what team did to develop this great Multiboot VU selector
yes that did, and i hope to have it on OBHNormally when you flash an image, it will reboot to that image slot(standard multiboot function), I think with OpenATV you can flash an image without rebooting.
For old images (OpenATV 6.4) read thisInstalling Multiboot.py adviced for OpenATV 7.x to OpenATV 6.4 didn't worked. After GUI restart the enigma GUI stopped working (no reaction to remote).
Fortunately WinSCP to box was still working so I decided to rewrite the content of file /boot/STARTUP with content of STARTUP_1 which is OpenBH 5.2 (Slot1). After reboot the box is working again...