It works only in gp3. The location was defined in the BP is used. This creates ipk enigma2.sh no entry in the backup so that one can be created. script is also installed in rc.3d one that checks for the required entry in the enigma2.sh, eg, the enigma2.sh replaced again with an update, the script detects this and patch the entry back inside. eigtl the backup and restore function works like this: - A epgbackup.dat is created when at least 1 MB epg.dat big. - Which will remain hidden and replaced by the epg.dat epgbackup.dat when epg.dat does not exist or is less than 1 MB. The script is for a slave box, i.e. This box must not create backup. That you just need to no if you mount the network sets epg.dat. It should also work on multiple boxes with the ipk, it must then stop all ne backup.dat produce boxes.
when installed CrossEPG a symlink from CrossEPG epg path can be created to gemini epgpfad. Thus, an installation should have no impact on CrossEPG. I do not even use CrossEPG habs and not tested but should work. I also got the log bissl spending review, it should now be meaningful depends what where.