It seems that work has subsided enough for me to keep a promise. Because I can be long winded (I think it necessary) when explaining how and why I perform particular tasks, I have decided to write several successive posts on this subject because I think it will be valuable, both to new Sparky Linux users and to experienced Linux veterans.
Taking the time to explain hings always makes sense to people learning but the Linux pros have a tendency to overlook the obvious because they work so fast. So, if anything I discuss interests developers, moderators, and hardened Linux users, then by all means check it out. At least it might be entertaining.
Before starting, I want to publicly declare my praise and appreciation by thanking pavroo and any other involved parties for their fine work in taking the old Remastersys project and reworking it using YAD to make it a valuable asset and useful timesaver for Sparky Linux users. I also declare that at no time do I take credit for any of their work. I simply spent many hours (and I do many many) attempting to use this tool as a means to help me save time in my charitable work. A long and drawn out number of posts have been previously provided explaining what was happening with me. Check out this area of the forum for those earlier posts. And now, let's get started.
One more thought before starting. There are several forks of Remastersys by other parties as well as similar tools that can be used with success (under limiting circumstances). I have used them as well as the complicated and time consuming live tools in Debian. I will save the uses and reasons of concern for those tools in another series of posts. After I finish outlining Sparky-Linux-Sys. Remember, I take no responsibility for mistakes, warranties, etc. Sparky Linux provides the proper disclaimers. Always make backups of any important files before starting.
The first question is as follows. Why do I want to use a tool like Sparky-Backup-Sys? Well, I rework older pc systems and donate them to anyone that needs them. Recipients are churches, schools, volunteer groups, rescue groups, public or private service organizations, and any individual(s) that may be short of funds to purchase new and more sophisticated hardware. In doing this work, I found myself spending a tremendous amount of time installing Sparky, Debian, etc., and configuring each machine. The age of the systems average between seven to twelve years old. I have even configured a few older than twelve years old but not many.
Based on those facts, the need to create a standard setup and install would save me a huge amount of time and time is the most valuable asset we all have. Additionally, my work demands that I work in a virtual environment to create a desktop configuration that is truly tailored for older pc systems, laptops, and notebooks. Once finalized and created, I use the tool to create a hybrid iso file, burn it to blank digital media or a usb thumb drive, then promptly boot, test, and install Sparky Linux / Debian with a minimal touch up at the end.
ACTUALLY, in the beginning, "failure" kicked me in the teeth almost every time. I was so mad because of so much lost time that I decided to experiment and test continually until I discovered what was causing my problems.
I discovered that there were two main causes of my failures. (and I bet everyone else as well) One was out of my control and caused by a newer version of Busybox that apparently caused grief for many other people just as it had caused for me. The good news is that Busybox no longer presents a problem, at least not for me in twenty four installations.
The other was completely caused by a simple issue that should have been obvious to me but I overlooked it many times. As I spent time configuring Sparky Linux to simplify its interface and reduce the software not needed for my purposes, I was constantly using root privileges to delete, remove, alter files and system settings as well as add themes, icons, artwork, etc. In all of my haste, I kept forgetting that the root user (su) and normal system user accounts store deleted files, etc. in trash folders (directories) until permanently removed. While I always made certain that the regular user system baggage was cleaned and sanitized, I ignored the root user's discarded system mess because it is hidden from the regular user. Remember, system wide directories, utilities, configurations, deleted files need admin access to perform system wide house keeping. The discarded system junk was piled high and deep.
Since hybrid iso files are read only squashed file systems compressed into a single file to be executed in memory, they are governed and restricted by the iso9660 IEEE specification and Sparky-Backup-Sys which do not allow a final iso size to exceed 3.99 gigabytes because of system overhead.
I found after testing over and over that exceeding 3.5 gigabytes sometimes caused problems. What's the root cause of this fact? Invisible code execution? Who knows except to say that software can be peculiar in its behavior in real world conditions. So rather than experiencing more failures, I now limit the FINISHED file size accordingly: 3.5 gigabytes or smaller.
The simple rule is don't install and configure everything including the kitchen sink. Just install and configure the utilities, services, and applications needed for regular usage and installation. More can be added when and if the iso is used to install on hardware.
Continuing, because there exists some inconsistencies and incompatibilities between similar tools created and used by other parties, I recommend that you completely uninstall those tools. As an example for instruction only the following is what I use to perform the task.
sudo apt update
sudo apt purge theothertoolname
then the following
sudo apt-get autoremove
sudo apt-get autoclean
NOTE: Caution is in order when using autoremove because of unintended results with xorg and system wide connected components. An example would be anything related to X. Use the man pages for apt, apt-get options to read the commands I listed and their functions in housecleaning. Next, I installed the following simple utility available in the repos.
sudo apt install trash-cli
Once installed, use the following command to clear out the hidden trash leftovers from the root user's account.
We need to keep in mind that the Sparky-Backup-Sys tool will include system directories and their contents. If the root user's trash and discarded junk isn't removed permanently, it will cause the the hybrid iso file to exceed its maximum allowed size. Although the regular user's home directories and their files are not included in the iso build, the following will clear out and remove all related trash as well.
trash-empty (sudo is not needed) for the regular user.
(part-2 will be continued on the next forum post and continue where I left you)
As an addition, I suggest to replace:
sudo apt-get autoclean
sudo apt-get clean
The 'autoclean' removes older version of deb packages if exist, the latest ones won't be removed.
The 'clean' removes all downloaded by APT deb packages from the system.
If you read my post to the end, you will see where I include autoremove and autoclean in the house keeping duties.
Thanks for your diligence.
Paul ( sasdthoh )
Yes, I did, but I only suggest to change the apt command of "autoclean" to "clean".
Ok, I have no problem with using "clean" instead of "autoclean." Can you enlighten me as to the reason you make that suggestion, based upon the man page options and explanations?
I already did:
QuoteThe 'autoclean' removes older version of deb packages if exist, the latest ones won't be removed.
The 'clean' removes all downloaded by APT deb packages from the system.
Clean removes all debs making the target iso smaller.
Autoclean always keeps the latest versions of debs of installed packages, you do not need in the target iso.
I'm sorry for overlooking a clearly stated explanation that already answered my question. I am seriously tired and it was a classic "DUH" situation on my part.
I wasn't questioning your wisdom, just asking to clarify.
In truth, you are correct to remove ALL deb files to make the smallest possible iso.
Can I assume I was basically spot on about the rest?
Thank you again!
Paul ( sasdthoh )
Of course, feel free to do so.
Part-3 How To Obtain Success Using Sparky-Backup-Sys Tool (Forked Remastersys)
Continuing from my last post, if you have completed the steps and considered the suggestions I detailed in my muti-part posting about this tool, you should now have a valid hybrid iso file, ready to burn to a usb thumb drive or a digital media blank disc.
The first thing I do is to make certain the usb thumb drive is not defective so I use the USB disk Formatter Tool available in Sparky Linux to format the USB thumb drive. If it is not installed in your system, use the Sparky-Aptus-Extra tool to install it as well as the Live USB Creator.
As always, you can use the lsblk command in the terminal to identify the usb thumb drive.
After a successful format, use the useful Live USB Creator to write your newly created iso to the thumb drive. For you terminal lovers, use the following dd command to write the same iso file.
sudo dd if=/home/filepathtoyourisofile/yourisoname.iso of=/dev/sdb bs=4096
This assumes your iso is located in the default location where the Sparky-Backup-Sys tool created the file.
Of course, the location of file will determine the path in the statement. For the purpose of an example, I used sdb as the system identifier of the usb thumb drive. Sparky Linux makes this process very easy but all that you need can be accomplished using the terminal.
In the Windows Desktop world I use either Rufus or Universal USB Installer to burn the iso to the thumb drive. The tools and methods I have described have never failed me as long as the iso is valid and the usb thumb drive is not defective.
Once the processed has finished, you can test the usb in any pc or laptop that supports booting from external devices like the thumb drive.
I am interested in your success so let me know whether or not you have problems following the posted instructions. I created another one earlier today using the exact same steps and it worked without issues.
I have more posts covering saving user configurations and my experimenting with using persistence. I will cover those topics when enough time permits.
Best Wishes and Good Luck!
Paul ( sasdthoh )
Part-2 How To Obtain Success Using Sparky-Backup-Sys Tool (Forked Remastersys)
Well, I wrote a very lengthy post for part-2 yesterday detailing the steps I take to prep and create the hybrid iso file. For some reason, I do not see it listed here. I can't explain it so I will take some time to write another post hoping that I will not have to repeat the process.
After explaining the procedures and issues in part-1, I take the following steps.
I use the graphical front end from the menus for Sparky-Backup-Sys to edit the Backup config file and the Installer config file.
In the Backup config file, the WORKDIR label determines the name and location of the completed hybrid iso file. While learning, I suggest to leave it alone. It will create the following folder (directory) by default where all the of temp work files do their magic.
I leave the LIVEUSER label the same. It serves my purposes because when I create the final iso file, it will use the username "live" and the password "live" until installing to actual hardware.
LIVECDLABEL is what appears at the top of the iso boot manager's initial display. I change it to something simple nut it's not required.
The CUSTOMISO label entry is where you actually name the iso file created. I always chnage this to something short and descriptive. Remember to keep it within quotes. In fact, make certain that the quotes never get accidently removed when changing labels.
Save and Exit.
Open the Installer config file. There is really only one label to contend with, the NewGrubDefLine. I remove the entry and leave just the quotes with no space between them but it's up to the user and not required. I have tried making changes to this option and the results are obvious. This one will be up to the user but you can ignore this if you choose. If you make any change on this option, don't forget to save before exiting.
Lastly, the Clean_Cache option removes all deb files in the system to reduce the final iso file size. I use the command line option to perform this task and will shot it momentarily.
DO NOT USE THE GRAPHICAL GUI TO CREATE THE ISO. For some reason, I have had mixed problems using the gui to create the iso. I have no idea why it doesn't consistently work for me so I now ONLY use the command line commands. Exit the gui and open a terminal.
Remember to use the house keeping commands and tools to make certain you system has removed all unnecessary junk and system leftovers.
A WORD ABOUT CLEAN AND AUTOCLEAN. I have always used AUTOCLEAN as a system house keeping command but pavroo is absolutely correct by stating the use of CLEAN instead. It removes all deb files while autoclean only removes deb files that can no longer be used by any package leaving current deb files remaining.
There is a case for using autoclean on installed Sparky Linux systems but creating the hybrid iso requires the smallest file size possible. It gives the user some leeway in adding other software to their build because more space is available assuming the user wishes to do so. Use the man pages to read a detailed explanation of the differences. It's quite educational.
OK, now is the time to create the iso.
Open the terminal, make certain to review you use of the house keeping commands, then issue the following command.
sudo sparkybackup clean (only use this command to remove any previous builds)
sudo sparkybackup dist
This will start the process and takes varying amounts of time, depending on hardware and system resources. Be patient. Also, do not use the system for other tasks while building the iso file. Get yourself something to eat, a favorite drink, read a book, whatever helps to pass the time until the process has completed.
Once the process has completed, use your favorite file manager and check the hybrid iso's properties to make certain the file size appears to be normal. My builds usually range between 800-megabytes and 1.1 gigabytes which depends on the system software and configuration choices. Yours could be slightly smaller or larger based on personal choices.
If all appears to be normal, read my post part-3 for instructions to burn this newly created iso file to blank digital media or a usb thumb drive.
Paul ( sasdthoh )
Question #1: Having in mind that in Sparky Backup System's guide Part-1 it is written that "NOTE: Caution is in order when using autoremove because of unintended results with xorg and system wide connected components." then why does the Clean_Cache command of Sparky Backup Sys uses the "sudo apt autoremove -Y" command?
Question #2: Isn't it even more dangerous and destructive once it uses the "-Y" option?
Question #3: Since the title of Sparky Backup System's command is "Clean_Cache", wouldn't it be more appropriate to either change the name to something like "Remove all orphaned" or to attach a command that really cleans the cache, like "sudo apt clean"?
Question #4: In addition, since in the last post it is stated that "Lastly, the Clean_Cache option removes all deb files in the system to reduce the final iso file size. I use the command line option to perform this task...", isn't this a clear sign that we all do the same mistake when we trust the Clean_Cache option of the gui? Especially when the exact command that is used by the user sasdthoh is not clearly stated. I guess that it is the "sudo apt clean".
Question #5: Furthermore, in the next sentence, we are advised not to use the gui to create the iso. Could the "Clean_Cache" problem be the reason for gui's misfunction?
May I guess that the Clean_Cache command, which uses the "sudo apt autoremove -Y" command, has destroyed some installations of some unlucky Sparky friends? In my installation, it deleted "grub-pc-bin" and "grub2-common", but I was lucky enough to boot again without having to repair anything. I later executed "sudo apt install grub2
" so as to re-install the missing files.
That's good point.
Removed the "-y" option from autoremove so it will ask for your permission now.
Anyway it has to be used to remove all orphaned packages.
I am happy that I helped. I think that nobody would deny the need to use it and it's effectiveness in removing orphaned packages. Though, the name Clean_Cache is misleading. Please consider changing the name in the gui and it's description.
I have noticed that the command "sudo sparkybackup clean" does not delete the same files as Sparky Backup System does when we double click on Clear.
The command "sudo sparkybackup clean" only deletes the folder /home/sparkybackup-sys/sparkybackup-sys, which hosts the previous builds. It does not delete the folder /home/sparkybackup-sys, nor the files inside /etc/skel/.
On the other hand, running Sparky Backup System and double clicking on Clear, deletes the folder /home/sparkybackup-sys, not only the sparkybackup-sys folder inside it, and the files that exist in /etc/skel folder. The gui option is more thorough than the cli one.
Shouldn't these commands be totaly equivalent?
Made all the changes and improvenments you suggested:
Test and report whatever you find, please.
Sparky Backup System has improved a lot and Pavroo has done very good job once again. Unfortunately, testing revealed some problems.
In Sparky backup gui, in the EFI option, the file name libefiboot1 should be placed before libefivar1, in order to correct the alphabetical order.
When I install by using "sudo apt install packagename", the /var/cache/apt/archives folder is emptied automatically when the installation procedure ends. This is a long awaited improvement, because there will be no need to clean the cache as often as before. Though, when I do the same installation with APTus, the deb file remains in the /var/cache/apt/archives folder. I think that APTus should be automatically emptying the cache too.
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". All correct here, so nothing to worry about.
Sparky Backup System > Clean did not delete the folder /home/sparkybackup-sys/. Though, the command "sparkybackup clean" worked as expected and deleted the folder /home/sparkybackup-sys/.
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/. The same actions are made by the command "sparkybackup skel".
This way, the created iso didn't preserve the settings that were made. This is not enough. It would have been more useful if it copied every file, hidden or not, that exists in the /home/user/ 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. 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. Of course, copying everything from the home folder means that the home folder should have already been cleaned-up and kept small in size.
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. It should simply return us to the main window, just like Sparky Backup System > Cache does.
Sparky Backup System guide
Sparky provides Sparky Backup System to make custom iso images. If you make a spin of existing iso image or a hard drive installation of SparkyLinux you have to:
1. Change the iso image name adding 'community', 'custom', 'unofficial' or 'remix' in the new spin's name.
2. Let all the people know that you made an 'unofficial' spin which is NOT made by SparkyLinux 'dev' team members.
Install Sparky Backup System, if it is not already installed. Run "sudo apt install sparky-backup-sys sparky-backup-core" for installing both the graphical and the command line interface. 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.
Part-1: Upgrading and cleaning (junk files, system leftovers and trash files)
Run System Upgrade Tool to upgrade the system. Otherwise, execute the following commands:
sudo apt update (to see the packages that can be upgraded, run 'apt list --upgradable')
sudo apt upgrade (to install the upgradable packages, if any)
(simpler as a joined command: "sudo apt update | sudo apt upgrade")
Run Sparky Backup System > Clean (or "sudo sparkybackup clean")
to delete the folder /home/sparkybackup-sys, which hosts the previous builds.
Run Sparky Backup System > Cache (or "sudo sparkybackup cache") to remove cached deb packages and all orphaned packages. It executes the following commands:
1) sudo apt clean (Removal of all deb packages from system's deb cache folder (/var/cache/apt/archives/). Never use "sudo apt autoclean", because it removes only the old deb packages).
2) sudo apt autoremove (Removal of orphaned packages. Use it with caution because unintended results may occur with basic system files like Xorg, grub, etc)
3) sudo aptitude purge ~c (which usually suggests to remove the same packages as "sudo apt autoremove" does).
-delete all inside /home/user/.cache/thumbnails/fail, /large and /normal folders
-review home folder's hidden files (especially .cache and .config) so as to delete folders, files, settings, history and leftovers of uninstalled applications.
-run APTus > system > remove old system kernel (the previous kernels are not usefull if the latest one works fine)
-Do not delete all inside /home/user/.cinnamon/spices.cache/applet, /extension and /theme folders because at the cost of 1MB, more readyness is provided.
If it is not already installed, install trash-cli package (with "sudo apt install trash-cli"), and execute:
1) sudo trash-empty (with sudo, for administrator's trash)
2) trash-empty (without sudo, for simple user's trash)
The trash-empty commands delete the hidden trash leftovers from root user's and simple user's account. If the root and simple user's trash files don't get deleted, they will make the iso file bigger. Although simple user's trash files are not included in the iso build, it is better to use the trash-empty command to delete them. The smallest the file size, the better. (simpler as a joined command: "sudo trash-empty | trash-empty")
Part-2: Deciding the default settings and files
After the preferred applications have been installed, make certain that all settings and preferences are set, like backgrounds, browser settings, theme preferences, icons, task bar appearance, prefered applications etc. Any kind of file may be added to user's home folder, at the cost of making the iso bigger. Delete any data that may reveal personal information. The user's home folder and default settings must be ready before following Part-3 guidelines.
-install new backgrounds: if you have a collection of backgrounds that are under GPL licence, you can add them in the distribution. Put the backgrounds in a folder and place the folder into /usr/share/backgrounds/ (root priviledges are needed). Copy from /usr/share/gnome-background-properties/ a simple xml file, with less than 15 lines of code, and paste it inside the same folder (usr/share/gnome-background-properties/). Rename the xml file, having in mind that the xml's filename will be shown in the left side of Cinnamon's background settings. Now, basic html knowledge is needed. Edit the xml so as to include 1) the path of every image file that exists in the folder and 2) a name for every background that is shown in the right side of Cinnamon's background settings.
-set the default background: The system uses as default wallpaper the "/etc/alternatives/desktop-background" file. The filename is "desktop-background" and it does NOT have an extension in the file name. It is a standard png graphics file, and so should the new wallpaper be. The filename must remain the same. Instead of replacing the original, back it up by adding a .bak extension (root priviledges are needed). Of course, the users of the created iso are able to change the wallpaper to anything they want.
-support UEFI booting: create the home/offline/ folder and place inside the following 6 deb files: efibootmgr grub-efi grub-efi-amd64 (or ia32) grub-efi-amd64-bin (or ia32) libefivar1 libefiboot1. Use apt-get download <packagenames of the 6 files> to downloaded them. Sparky Backup System will later copy them to the /etc/skel/ folder, together with the other /home/user/ files. The same instructions can be found at Sparky Backup Sys gui > EFI. UEFI works with Calamares installer (sparky installer) and with Sparky Advanced Installer.
-Home folder: delete all unwanted files inside the, not hidden, subfolders of the home folder (downloads, pictures, etc).
-Firefox > Preferences > Privacy and security > delete saved logins, clear history "time range: everything" (for deleting EVERYTHING and feeling safe), clear Data. Uninstall not usefull addons (possibly disable ublock origin).
-delete all keyboard layouts except of US-English.
-set the sound volume to 100%
-clear libreoffice's recent documents
-clear media player's recent documents (qmmp, vlc) and set the sound volume to 100%.
-toggle Nemo's location entry to "breadcrumbs", preferences/toolbar/show home button
-Nomacs: edit /home/user/.local/share/nomacs/settings.ini to remove recent files and folders history. Nomacs must have been executed at least once for this.
-update all files inside /user/offline/ folder. Use apt list <packagenames of the 6 files> and apt-get download <packagenames of the files in need of update>. No need for superuser rights in both commands. Alternatively, apt-get download <packagenames of the 6 files>, move them to /user/offline/ folder and delete the old ones.
-update anydesk.deb in /home/downloads/ folder. If Anydesk is installed, it must be purged, together with it's dependecies (anydesk libgtkglext1 libpango1.0-0 libpangox-1.0-0). After removal, delete home/.anydesk folder. The reason for the removal is that the username, which is generated by Anydesk, will stay the same for everyone who will use the iso of the distribution. Copyright prοblems may occur too.
Part-3: Copying settings and creating the backup
Run Sparky Backup Sys gui > Skel (or "sudo sparkybackup skel")
The skel command empties the /etc/skel folder and afterwards copies there all the files (and the hidden ones) from /user/home/.
Though, sparkybackup skel (both gui and cli) does not work as expected (*). Until it works the way it should, we have to start a file manager as root, set it to display the hidden files and folders and:
1) navigate to /etc/skel/ and delete everything inside it.
2) go to your user's home folder, copy everything, including all hidden items, paste them into the /etc/skel folder and close the file manager.
(*)The /etc/skel/ folder is deleted every time we use the "skel" command (gui and cli version) but both gui and cli version fail to copy everything from /user/home/ folder to the newly created /etc/skel/ folder. They both deleted the skel folder, created a new skel folder and placed inside only some hidden files of the /user/home/ folder.
The above commands are executed again, because the deletions that we may have made with the previous file handling should not remain the trash folder.
Run Sparky Backup Sys gui > Edit (Be carefull not to remove the quotes when editing)
-WORKDIR no need to be changed
-LIVEUSER no need to be changed. The iso file that will be created, will use the username "live" and the password "live" until installing to actual hardware.
-LIVECDLABEL is what appears at the top of the iso boot manager's initial display. Change it to something more self-explanatory. (i.e: LIVECDLABEL="SparkyLinuxCinnamonRemix")
-CUSTOMISO label entry is where we actually name the iso file that will be created. It should be something short and descriptive. (i.e: CUSTOMISO="sparkylinux-5.4-x86_64-cinnamon-remix.iso")
-VOLIDxxbit no need to be changed
Run Sparky Backup Sys gui > Installer
-NewGrubDefLine no need to be changed. The entry may be removed, by leaving just the two quotes with no space between them, only if the user can understand the results of this change. (NewGrubDefLine="quiet splash")
Close all programs that do not need to be open.
Run Sparky Backup Sys gui > Dist (or "sudo sparkybackup dist")
This command starts the process of iso creation and may need varying amounts of time, depending on hardware and system resources. It uses 100% of the cpu and needs at least 8 minutes (or 37 under virtualbox). Do not use the system for other tasks while building the iso file. Once the process has been completed, use the file manager and check the hybrid iso's properties to make certain that the file size is normal. Test the iso file by writting it to an optical disk or a usb drive and trying to use it.
If a usb thumb drive with persistence is the target, users should read the special thread of Sparky Linux Forums about it.
Athough I have written it in the previous reply, inside the Sparky Backup-System guide, rephrasing it may help solving the problem.
As far as I know, the skel command is supposed to empty the /etc/skel folder and afterwards copy there all the files (and the hidden ones) from /user/home/.
Though, when using Sparky Backup Sys gui > Skel or "sudo sparkybackup skel", things do not work as expected.
At start, everything goes well and the /etc/skel/ folder gets deleted every time we use the gui or cli version of the "skel" command. Then, a new skel folder gets created and placed inside.
The problem is what happens next. Both gui and cli version fail to copy everything from /user/home/ folder to the newly created /etc/skel/ folder. Only .cinnamon folder, .config folder and 4 hidden text files of the /user/home/ folder get copied. I have been using it since May 2018 and I never saw it working as I expected. Latest Sparky Backup version tested: 20181127.
Thank you very much for this thread. :) Much appreciate. I've been able to create an iso, but it wasn't bootable/seen in the bios menu (needing to do UEFI-booting iso) ... I'm doing the process again, and have the 6 deb files in a folder called 'offline' in home directory, as before, but can see now that they aren't copied over into etc/skel. Just to ask which folder the 6 debs need to be copied into in skel.
I've just seen another thread about remastering, and it says there should be 5 dirs, but, if I open the iso in engrampa, it shows three folders: BOOT, isolinux, live.
BOOT contains Boot-NoEmul.img. Unfortunately no EFI or offline folders.
The tool's broken? That's all I can gather from no responses.
Following the backup tool instructions, it works very well
and I'm sure a response is not needed to justify that.
The 6 files are not copied to etc/skel.
They appear in the /home/sparkybackup-sys/ISOTMP/offline folder needed to create the iso and are probably part of the 5 folders you refer to.
I followed the instructions. It didn't work, so a response turned out to be needed. Whatever the 6 debs have done, the folders needed are missing, so not seen/bootable. No worries. Had appreciated the (2018/abandoned?) tutorial here, but that's why I said maybe the package is broken, as, despite following this tutorial, things didn't work and there's not much else to read. Complicated business, and am not very tech, so am learning about MX Linux and glad of beginner-level tutorials, even though have been on linux since 2017. With too much changing on Linux, although I really am impressed how well Sparky runs and feel it should be a lot more popular, need to futureproof stuff, and have stronger backups generally. Anyway, good luck to Sparky.