Development > Remastering

Part-1 How To Obtain Success Using Sparky-Backup-Sys Tool (Forked Remastersys)

<< < (2/5) > >>

I already did:

--- Quote ---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.
--- End quote ---

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 )


[0] Message Index

[#] Next page

[*] Previous page

Go to full version