FINALLY! Some Success With Sparky Backyp Sys and some Important Info

[sasdthoh]

If anyone has been following my many long hours  and multitude of failures while trying to use the Sparky-Backup-Sys as a reliable tool in my work for charitable interests, I can now officially announce that I have made some discoveries in the general use of that tool and also have successfully created hybrid iso's in a virtualized environment that REALLY WORK outside the vm's and on real hardware.

For a long and drawn out reference, open the other threads by me in this section and read all of my previous posts.

Anyway, the Sparky-Backup-Sys tool is a fork of the original Remastersys project. I don't mind telling everyone interested that pavroo and the rest of the developers have done a GREAT DEED in providing, or attempting to provide such a useful and educational tool.

I now have identified the number one culprit in failures while I was attempting to create working hybrid iso's. It is not the only one but it is the one cause that has plagued me the most.

As soon as I have finished my current billet of work, I am going to sit down and provide, in detail here on this forum, an abbreviated explanation of how I use the tool and the steps I take to almost eliminate any failure in the process.

Not to be offensive and to be plainly stated, this software served to "piss me off" so much that I was determined to solve the issue, once and for all, no matter how long it took.

I am retired now but back in the day, I was a damn good database programmer and operating systems specialist. But my professional experiences were not with Linux. It wasn't created yet or it was still in its infancy.

I have made another promise to myself. When time permits, I intend to brush up on my programming skills and improve this type of tool to such an extent that failures becomes almost an impossibility so long as it is configured and used correctly. When I succeed at that time, all of my work will be donated to Sparky Linux, its developers, and the entire Sparky Linux International community exclusively to show my appreciation for such a fine Linux Distribution.

"Contributing To Rock Your Sparky Linux World!"

ps: I have some really cool surprises in store for everyone. Stay tuned.

Best Wishes To All and Thank YOU!!!

Paul ( sasdthoh )

[godstand2]

Do not place much stuff in the /etc/skel directory. It breaks the live system and it won't start. How much is much stuff can i put the stuff from my home/(username) folder in there?

[sasdthoh]

Have patience. I'll be finished with my current work billet soon so I will have the free time necessary to provide some insight and simple steps to make your efforts a success.

Stay Tuned, (hopefully by the weekend)

Paul (sasdthoh)

[pavroo]

It wasn't clear, I already fixed the wiki page.

It means, you should copy your customized desktop's config file only.
Copying other, personal files breaks the live user configuration during the live system starts.

The GUI option called copy to skel copy as many desktops configs as posiible (as you have) and nothing alse.

Time ago I moved 500MB of steam files to skel and the system's user did not start.
I also moved another application config, not bigger than 5 MB and the result was the same.

So, if you have any extra stuff, not installed, placed them in /opt for example.

[godstand2]

I really love SparkyLinux the most of all distros for it is sooooo fast on all computers Old and new(by the way the 32bit is what I use even on 64bit computers). I was wondering after I have already set up my sparky how can I make a backup disk with all my settings and apps and not just a hybrid iso like sparkybackup dist does and keep it for an emergencies to install it to say another computer, Like I can with Systemback does.It also gives you the option to install for a new user. I had installed System back on Sparkylink test machines and tried to use the copy user data and settings box checked and it said that it could not read Live image even when i tried to install the same thing happened, from the ISO I had made of the system using Systemback. I could run the live cd but not copy or install even with out box checked for user data and settings always "Could not read Live image error." I have made an ISO from Sparkybackup dist and it runns with all the the stuff i put in root folder including wine,games and programs as long as I installed them in root folder running as root also settings for root like themes and cursors the live disk ran with out a hitch even installed on another hdd but not with users setting or data was the image made so i would have to start all over again to set up slimjet browser for the user that is only browser I use as well have to setup appearance,screensavers,cursors and so on.All this work time and energy makes johnny boy here tired. It would be so nice to copy my system to my other computers with all settings and data intact and also from same disk install for new user with the little bit of the extras I have installed in root.The Sparkybackup ISO was 1.9GB size when I got done making it using the xz setting.

[pavroo]

There are a few cases:

1.

i would have to start all over again to set up slimjet browser for the user that is only browser I use

The tool doesn't copy applications settings. They are too big and breaks live user settings.

2.

as well have to setup appearance,screensavers,cursors and so on

They are desktop settings so should be copied by you from your home directory into skel.

3.

It would be so nice to copy my system to my other computers with all settings and data

Sparkybackup sys doesn't let you do that, sorry.
Means, no all settings and data. If you copy your desktop settings, such as: wallaper, theme, icon set, panel position and its plugins stored by the desktop configuration files to skel - they will be recovered and used in a live system.

4.

i tried to install the same thing happened, from the ISO I had made of the system using Systemback. I could run the live cd but not copy or install even with out box checked for user data and settings always "Could not read Live image error."

I don't provide support to systemback tool, sorry.
But, if you made iso image using systemback, and used its live installer - the two tools shold be compatible each others.
I suggest to contact to the systemback developer.