Original von msurg
The main reason doing this is because the HDD is very noisy..
Here is what I did..
I backed up my Gemini image with backup-image tool. Then disabled BA with "ba.sh disablebootmanager".
After that I uploaded the backedup Gemini image into Flash and rebooted. And after dream 600PVR logo (before BA this logo wasn't showed) Gemini image came up. At this point I want to ask whether this Gemini image is working from HDD or from Flash?
The problem is I think that I haven't understood the working principles of BA. When I choose an image on BA does it upload it into flash or boot it from a partition from HDD? Sorry this may be a dump question but I am trying to understand how things are working
Thanks for your answers and patience
Understanding is the next step to enlightment !
Well, if you have the proper cables and adapters you could also add a CF card(internally), but this is not really tested (yet).
After a Flash the image doesn't know about Barry Allen and will always boot from Flash, so don't worry.
And if you are unsure you can always use ba.sh info to find out what is booted (or look for a /.bainfo file - this shows that you are booted form an BA image from CF/Harddisk - if you do cat /.bainfo you will even see the name of the image as entered during extract), if there is none you are (still) in Flash.
If you select a BA image for booting it will NOT be put to flash, simply after the selection of the image the kernel bootprocess will be chrootet to the image root on CF/harddisk for the rest of the bootprocess and continue working from there - hence the Flash kernel is still running and used from flash (with the few drivers needed by the bootmanager to be operational - unless you disabled it), but all binaries, setings,.. come from the harddisk/CF choosen image directory.
And BA doesn't use partitions onHarddisk/CF like Multiboot does, it just uses chroot to fake a new root from a directory of the BA device (/media/ba/ba/<imagename>
Wenn you do ipkg install or ba.sh patch it simply re-creates a few links (/ba and /media/ba to be honest and in an enigma2 image also the link to the Plugin and webif binaries) and replaces the init link with a link to bainit, the script which starts the bootmanager and does the chroot based on what you selected. Init is a tiny programm in nix whichstarts all other processes - if you 'chroot' it then you can switch to another image, which is excactly what flashwizzard, Dreamflash and also BA do.
Hope this makes clear how things work together.
PS: and you don't need to disable bootmansger before flashing, this is just to hide BA if you don't want it to be shown during boot.