I have a question about updating with bootberry.
When a new version of bootberry is released, is it simply a matter of replacing the content of the FAT32 partition on my SD card with the new version? I assume the new version will be able to read the ext4 data partition as is?
Theoretically it should be able to work that way, but my experience is that it doesn't... :(
I did replace the FAT32 content in exactly this way, and lost access to all installed OS (several RasPlex versions, and other stuff).
It didn't matter all that much to me, since I was going to use a new card anyway, switching to an SDXC model for its larger size of 64GB (beyond the SDHC limit of 32GB).
For updating rasplex itself inside bootberry, I suppose I can just install the new version, and then delete the old version, and reconfigure rasplex as needed correct?
That does work fine, and you can also keep old versions around for comparison if you like, installed in parallel under BerryBoot.
I always keep one copy each of the latest stable releases this way, as well as several beta test versions.
But that's because I'm a beta tester for the project. As a normal user I'd settle for the last two stable releases.
That will allow you to keep using a version you're happy with in case a new release turns out to have bugs or feature changes you can't stand.
Is it possible to replace the rasplex .img files directly with a new version without deleting it and adding it again?
I don't know a safe method for directly manipulating images already installed under BerryBoot.
It can probably be done, but it would require some experimentation to establish safe usage boundaries.
But you may be able to perform some future updating of RasPlex versions using its internal update commands.
I've never had occasion to try this with the RPi2 yet (only one official release exists), but it did work for older versions on the RPi1.
Thus I was able to use the internal update method to update RasPlex under BerryBoot from RasPlex 0.4.1 to 0.5.0.
But I wouldn't advise using this method to update from a current version to one of the next generation (RasPlex 0.6.x+), since this will use a new OpenELEC version, and I'm not sure if the old auto-update routines can handle that transition.
mpeg2 licenses installed in bootberry's config.txt applies to all OS installed in bootberry, very nice.
Yes, since the license is tied to the hardware serial number it applies to everything running on the same RPi.
It's only if you move an existing card to another RPi that the license usage will fail.
Lastly a technical question. I noticed bootberry have a "recover" option to reset the image. I assume it's keeping the original image somewhere in the SD card for this purpose. My question is does it runs off of this image (like mounting an ISO file and read the files directly), or does it extract the image to a working directory (and work with the copy)? I assume it's mounting the image file directly and recover simply blows away all the data/configuration file associated with the image correct?
To be honest I've never tried it, so I can't say for sure. But my guess is the same as yours.
All in all a very nice utility. I think the only bug I found so far is in some of the bootberry configuration screens, the tab order is slightly off. Also the long mouse hold to get the option of add image from USB is kinda non trival ;)
I agree, and people who use TV remotes through CEC must be especially frustrated with this, as it's impossible to use the BerryBoot configuration menus without a mouse.
I use a mini-keyboard with a built-in 'air mouse', and aiming this correctly while pressing the mouse buttons is quite a chore, as the mouse pointer tends to wander when pressing any key/button...
So when using BerryBoot I usually connect a normal keyboard+mouse combo in addition to my mini-keyboard (that's needed for the Linux desktop OS's installed anyway).
Best regards: dlanor