myDSL Extensions (deprecated) :: Extension loading order



I hadn't thought of that....so what happens is that backup.tar.gz gets copied to $HOME, overwritten in part by the icewm extension, and then re-written during restore?
what happens is:
first myDSL-extensions are loaded. (backup.tar.gz is skiped during autoloading of extentions).
then at the end of init 5 just before bootlocal, dsl-restore is called

so first the extensions setup the default settings in home THEN restore overwrites with user settings.
Yes, both of these suggestions will produce the desired result (tested yesterday).  Funny, zzz.dsl is exactly what I used!  However, I believe they merely work around some rather short-sighted design decisions in the construction of the various .dsl files which will limit their cross compatability and flexability.

I need to do some more research & testing to be sure, but I want to work within the "design plan" for DSL for the reasons that roberts cited on the prior page.  I think backup/restore is really intended for non-static data on writable media.  This, of course, includes config data but also requires a boot line argument.  Additionally, stuff placed into backup.tar.gz is of no use to anyone else.  :cool:
Quote (Guest @ Sep. 21 2004,10:27)
what happens is:
first myDSL-extensions are loaded. (backup.tar.gz is skiped during autoloading of extentions).
then at the end of init 5 just before bootlocal, dsl-restore is called

so first the extensions setup the default settings in home THEN restore overwrites with user settings.

Why is backup.tar.gz skipped?  If it's in the root of the CD, wouldn't it be loaded automatically along with *.tar.gz extensions?
if you look in /etc/init.d/dsl-config you will see it is skipped in linenr 11.
Next Page...
original here.