Thema: Backup sys settings and image from CLI

I have 3 pieces of Zgemma working with OpenATV. I do not use Multiboot in any of the receivers. The process of manual update/upgrade, backup of system settings and creating a backup image of the system, performed from the remote control via GUI, is "annoying", especially as it has to be done regularly on 3 devices.
Therefore, I would like to automate this process. At the moment, once a week with cron I run a system update / upgrade and then reload the device.
After that, however, I would like to backup the system settings and make the current system image. The resulting files would be loaded onto the Google drive.
My assumption is to keep 4 copies (from 4 consecutive weeks) in case there is a bug in the OpenATV repository again.
Of course, I can do the issue of creating system settings and a system image myself. But in Enigma2 there are some ready-made commands/procedures which when run will create the above-mentioned files on HDD or SD.
Question. How can I run these procedures (what syntax) from the CLI instead of the OpenATV GUI?

Hi. Update via the command line / Shell works nice, but I'm not sure if the update / overwrite of old files in the case of SKIN is solved. OpenATV uses some add-ons / settings in the SKIN and will be rewrited during the update and must be backed up before the SKIN is updated and must not be rolled back after the SKIN is updated / overwritten. Perhaps this is already solved in the update via Shell directly in the SKIN packages (OPKG tool), and not only in the GUI update. Updating via Shell is very simple, for example:

Code:

#!/bin/bash

init 4; sleep 5           # stop the Enigma... and waiting 5 seconds for Enigma to stop completely
opkg update && opkg upgrade
init 3; sleep 120         # start the Enigma... and waiting 120 sec. for the complete Enigma to start

wget -q -O - http://127.0.0.1/api/powerstate?newstate=5 > /dev/null 2>&1       # switch Enigma2 to Standby, because at startup Enigma2 is usually run in "online" mode

exit 0

As far as backup is concerned, in my opinion it is enough to back up only the Enigma configuration, icons and your own add-ons (softcam configuration directory, softcam binary, additional third party plugins that you will not find on the OpenATV feed server, etc.). For this purpose, I personally use my shell-script (it is necessary to edit the directory and files to back up):
- script preview: e2scripts/backrest at master * s3n0/e2scripts * GitHub
- script download: https://github.com/s3n0/e2scripts/raw/master/backrest


It is also possible to create a function for the shell-script that will control the RCU via the OpenWebif interface. It is possible to do so. But first you have to wake up Enigma from Standby, artificially send the "RCU button press" to OpenWebif (Enigma updates and subsequent Enigma image backup) and then activate Standby mode again. However, this is inefficient (in case of any error, the script will still send button codes via openwebif and ignore errors and this can be undesirable).


Shell scripts can be run scheduled via the Linux CRON service (scheduled tasks in OpenATV can be found in this file: "/etc/cron/crontabs/root").

Ofgwrite is used to back up the contents of the flash memory in the set top box, but I don't know how to work with it ... I would have to study a lot about it again. Or is it just for writing an image to flash? I don't know, sorry.

GitHub - oe-alliance/ofgwrite: ofgwrite from Betacentauri: Based upon: mtd-utils-native-1.5.1

ofgwrite is used to flash. For backup the integrated image backup function (more different parts and even steps) is used. Therefore someone must jump through the whole process from remounting, stopping services, ignoring deeplinks, to making an archive of kernel- and root-partition, and clearing up after the process.