Why Gemfury? Push, build, and install  RubyGems npm packages Python packages Maven artifacts PHP packages Go Modules Debian packages RPM packages NuGet packages

Repository URL to install this package:

Details    
enigma2-plugin-extensions-dbackup / usr / share / doc / enigma2-plugin-extensions-dbackup
  ..
  README
  changelog
  copyright
Size: Mime:
This is the README of dBackup3 Plugin for DreamOS

It allows you to backup your DreamOS Image and Flash it directly 
from the dBackup3 Plugin.

It will ONLY support Flashing when booted from the Image in Flash!

@@@ Why are the old Dreamboxes NOT supported?
Since end of the year 2021 gutemine supports ONLY recent 
Dreamboxes - eg. one/two/seven with DreamOS Images.
Only these support the latest Development OE, will 
support Python3 and have sufficient CPU power to 
support the @ Plugin.

@@@ What about support for my old dm9x0?
Since purple day release, there is also a totally UNSUPPORTED 
Version of the gutemine3 Feed plugin for the armhf architecture
available on the gutemine3 Feed, which allows to run the 
dBackup3 Plugin and some selected other plugins on the dm9x0.
BUT do NOT expect any support, future versions, or comparable
performance on these old Dreamboxes!

@@@ Why is the code of some of gutemine's Plugins NOT modifyable?
Due to the misuse of some of my pluins, the gutemine3 Feed, the
User Scripts and the dBackup3 Plugins are NOT modifiable, despite the
Python sources being shipped and included in the installation kits.

@@@ Why does the backupname always contain the boxtype, 
dreamone/dreamtwo/dreamseven/dm900/dm920, even when I remove it?
This is AUTOMATICALLY added, and the protection to prevent 
flashing/booting wrong images which are NOT made for a box and 
could cause damage of your Dreambox. This functionality will 
be probably modified when Dream Property will introduce the universal 
images - which will then be flashable/bootable on ALL the OE2.6 
Dreamboxes.
Therefore it is NOT possible to disable this protection and if 
you use fake/wrong boxnames in your imagenames then face
the potential consequences.

@@@ Why can't I rename the backup image to whatever I want?
See answer to previous question, this is to protect you box from 
flashing/booting wrong images. If you want to rename an image 
to get afterwards the same name and Imagename in the imageselection 
this is the WRONG approach. 
Image names NOT following the naming convention 
will simply NOT be shown in the List of images.

@@@ What is this date and time setting about?
If enabled this will AUTOMATICALLY add the current date and/or 
time to the imagename, hence it is wrong to type these yourself 
in the imagename, unless you want it twice. 
If you do NOT want this behavior simply disable these settings.

@@@ Why is the prefix that I have setup ignored on Merlin 
and Newnigma2 Images?
Because on these images the creator is picked from /etc/image-version 
file, In standard DreamOS Images they contain no creator.

@@@ Is the date/time if enabled and boxtype deducted from the maximal 
Image name length specified in the setup screen on menu ?
Yes

@@@ Why is the backup in the dBackup3 Plugin so slow?
Probably because you simply didn't install the optional 
pigz, pbzip2, xz and tar binaries from the Setup
Screen on Blue. Then your backup runs on a single CPU core
with the busybox binaries. Only when these binaries are installed
full parallelization will be done and the full performance of the
Dreambox is used. 

@@@ Why is tar.bz2 NOT selectable as backup format?
This will be only shown when pbzip2 binary is installed.

@@@ What is this superspreader plugin functionality?
gutemine3 Feed, Alan Turing, dBackup3 and UserScripts Plugin
are superspreader plugins, meaning if they are installed in the 
Flash they will also be available in DreamOS Images booted via @.
AlanTuring, dBackup3 and UserScripts Plugin will also 
spread to Open Images.
Except the @ Plugin (which may be only installed in the Flash
image) you may install all these Plugins also locally
in DreamOS Images booted via @. Keep in mind, that
NONE of my Plugins is allowed to be installed in 
Open Images, neither booted via @ or when
OpenImages are directly booted from the Flash of 
your Dreambox! If you try to circumvent this limitation,
face the consequences!

@@@ What are the traffic lights on the About screen for?
The left most shows if the test kit is in his validity period.
Green means all OK, yellow means last week before expiration
and a red one means that the test kit has expired and only
basic functionality is left. Expired kits for example
will NOT allow to boot images with @ or flash images directly
from dBackup3, etc.
The left traffic light becomes also Red if a manipulation of my
Plugins is detected and the GHOST RIDER will be activated.
The middle traffic light indicates if Open* Images are supported 
for booting with the @ plugin and the number 2 or 3
number in the cirlce indicates which python 
version currently the feed plugin is running on.
The right most traffic light indicates if the 
GHOST RIDER removes and blocks panels, plugins
and feeds of people who violate my right as
the author of my plugins.

@@@ Why then this prohibitive signs when flashing with dBackup3? 
This is for information purpose and indicates where you 
may complain that these people and teams are violating my right
as the author of my Plugins and indicate that you now have to 
suffer from gutemine's reaction to their wrong doing.

@@@ What is this GHOST RIDER protection?
As a starting point I recommend watching the 2007 movie with Nicolas Cage
starring as the Ghost Rider, or have a read of the original 
Marvel Comic books series. Then be gutemine's guest and as long as 
you are NOT a Blackheart you have nothing to fear and the GHOST RIDER
will not come after your souls.

!!! Have fun with the dBackup3 Plugin !!!

gutemine