Restoring user's settings?

[labeas]

What  is TC's recommended/proven method for users to restore
their chosen setting made to the apps, so that they don't need
to repeat the same setup procedure for each reboot.

=> find location of settings
=> save RAM:tree to USB:tree by calling a shutdown script
At Re-boot:
=> in SetupScript
=> copy USB:tree to RAM:tree

But there are complications eg. need to allow for
USB mount <name> to change, depending on what's plugged.

PS. I'm still googling to know how to use the apparently
installed & working WiFi.

[coreplayer2]

Hi Labeas

I think you would really benefit from reading the " Book " downloadable from here http://tinycorelinux.net/book.html
to learn how TC operates.


BTW, the recommended method to achieve persistence of custom files on subsequent reboots is to add these individual files to your backup.
This is just one form of "persistence"  you'll find others in the book

There is a "BackUp/Restore" gui in "ControlPanel" to assist with adding files to /opt/.filetool.lst that you want to keep.  Also you can add files to/opt/.xfiletool.lst
for files you wish to exclude from the backup.
Or you may enter

Code: [Select]

filetool.shto view available options

Backup is enabled by default.  You may need to verify that  a backup file exists,  if not then create one by first verifying there is a file in filetool.lst to backup then use

Code: [Select]

filetool.sh -b
a backup file is created in the tce directory, usually named something like "/tce/mydata*.tgz

Then you only need to add custom config files to .filetool.lst followed by running the backup tool to save the files.

You can also use this command to make a quick backup

Code: [Select]

backup

 

[labeas]

> I think you would really benefit from reading the " Book " downloadable from here >http://tinycorelinux.net/book.html
> to learn how TC operates.

Yes thanks.
That confirms the several new requirement, for TC's fast operation.

[patrikg]

And if you add "v" to the filetool.sh you could also see what files being backed up.

like:

Code: (bash) [Select]

filetool.sh -bv


[labeas]

>   Then you only need to add custom config files to .filetool.lst.
>   followed by running the backup tool to save the files.
.
No! Serious applications have the settings saved in several fileTREES.
They are DESIGNED on the assumption that the sweated-labour setting of the users
will be saved in what ever format and where ever the designer has chosen.
Apparently by convention in the user's /<home> directory eg. /root/.config/mc/mcedit

With great difficulty and inconvenience, I can restore the settings of mc, because
I'm familiar with it's layout. But the opera-12 that I fetched is useless under TC,
since it has a mass of settings: mail, NNTP: User-ID, Passwords, Server:URLs ..etc.
---------
TC's <book> casually mentions <you may want to preserve your printers settings>.
Don't they understand that for serious usage: stable but possibly evolving setting
are essential for non-trivial programs?
------
To save and restore the settings the user would need to analyse/trace WHERE the.
setting have been designed to by located.
----
How will you handle an NNTP client which has 20 subscribed newsgroups [out of the
list of 60'000 - which also needs to be kept] and with an average of 30 recent
headers for each subscribed group ?
---
TC could design it's own apps to fit it's run-from-RAM concept, but can't handle
software that is designed to EVOLVE in peresistent memory.
You could even design a utility where it was impossible to locate the settings
retained for the next session.

[Misalf]

Tiny Core is not a ready-to-go distro but a tool-kit to create your own or whatever you want. Whatever config files you want to survive reboots just need to be added to your backup if they are located outside of $HOME.
While you're still complaining about this design after 75 posts here on the forums, I highly suggest you get out of here and pick another distro, because Tiny Core obviously is not what you want.

[Greg Erskine]

hi labeas,

I think you have missed the whole point of Tiny Core and need to invest your time in a Linux distribution more suitable to your requirements.

The guys here are NOT inexperienced idiots, they have designed a fantastic system.

regards
Greg