- Sparky linux reviews 2017 install#
- Sparky linux reviews 2017 upgrade#
- Sparky linux reviews 2017 verification#
Run System Upgrade Tool to upgrade the system. Part-1: Upgrading and cleaning (junk files, system leftovers and trash files)
Sparky linux reviews 2017 verification#
When the iso creation procedure will have been completed, there will have been created three files: the iso file, a file with iso verification codes and a list with the installed packages and their versions.
Sparky linux reviews 2017 install#
Run "sudo apt install sparky-backup-sys sparky-backup-core" for installing both the graphical and the command line interface. Install Sparky Backup System, if it is not already installed. Let all the people know that you made an 'unofficial' spin which is NOT made by SparkyLinux 'dev' team members. Change the iso image name adding 'community', 'custom', 'unofficial' or 'remix' in the new spin's name.Ģ. If you make a spin of existing iso image or a hard drive installation of SparkyLinux you have to:ġ. Sparky provides Sparky Backup System to make custom iso images.
It should simply return us to the main window, just like Sparky Backup System > Cache does. Sparky Backup System > Dist works correctly, but if we change our mind and press exit, when we see the "Click OK to create a backup iso now", it closes the program. Of course, copying everything from the home folder means that the home folder should have already been cleaned-up and kept small in size. The way Skel option works now limits its usability, because the user still needs to delete all the files at /etc/skel/ by hand, so as to be sure that the files which will afterwards be copied into /etc/skel/ will be the exact ones that the user wants to be in skel folder. After this action is completed, it would be helpful to show a reminder that the user should delete from /etc/skel/ the files that should not be included in the iso. It would have been more useful if it copied every file, hidden or not, that exists in the /home/user/ folder. This way, the created iso didn't preserve the settings that were made. The same actions are made by the command "sparkybackup skel".
Sparky Backup System > Skel deleted all the files that existed in the /etc/skel/ folder and right afterwards copied, to etc/skel/, only some basic settings of /home/user/. Though, the command "sparkybackup clean" worked as expected and deleted the folder /home/sparkybackup-sys/. Sparky Backup System > Clean did not delete the folder /home/sparkybackup-sys/. All correct here, so nothing to worry about. Sparky Backup System > Cache removes all deb packages from system's deb cache folder (/var/cache/apt/archives/) and exactly the same is done by the command "sparkybackup cache". I think that APTus should be automatically emptying the cache too. Though, when I do the same installation with APTus, the deb file remains in the /var/cache/apt/archives folder. This is a long awaited improvement, because there will be no need to clean the cache as often as before. When I install by using "sudo apt install packagename", the /var/cache/apt/archives folder is emptied automatically when the installation procedure ends. In Sparky backup gui, in the EFI option, the file name libefiboot1 should be placed before libefivar1, in order to correct the alphabetical order. Unfortunately, testing revealed some problems. Sparky Backup System has improved a lot and Pavroo has done very good job once again.
0 kommentar(er)
