Configsave should not be used anymore.

You may use:

dir2lzm /mnt/live/memory/changes /mnt/your_usb_stick_with_slax/slax/modules/config.lzm

If you like to save only small settings, simply create small slaxsave.dat and use it.

For example, a 1MB slaxsave.dat:

dd if=/dev/zero of=slaxsave.dat bs=1k count=1k
mke2fs slaxsave.dat

Then, save this file in YOUR_USB_DRIVE/slax/slaxsave.dat if you are using USB Slax, or save it in ANY_WRITABLE_DISK_OR_USB/slaxsave.dat if you're using the ISO version (and boot with second boot option).

People should really learn how to use the Persistent changes feature.

documented on: Apr 16, 2007, Tomas

> For these things i'm using /slax/rootcopy ... works fine

No it does not. Tomas and others (with whom I concur) have reported that /rootcopy isn't a wholly reliable means of bringing files into the system, for lack of file modes+ownership info. In fact, Tomas was on the verge of removing that feature from Slax 6, quite recently. Unless it's only a matter of importing data, one can never be completely certain the /rootcopy mechanism will work. Even in the case if importing data, file modes+ownership issues could unexpectedly bite you in the ass.

I haven't used CONFIGSAVE in at least six months, nor have I even tried the persistent filesystem trick (altho I must change that soon.) DIR2LZM/DIR2MO serve well, in fact have never failed.

mkdir -p /temp/root
cd /temp
cp -R /root/.kde /root/Desktop /root/.mozilla /temp/root
dir2lzm . /mnt/hda1_disk/root.settings.lzm

Those five commands will save your KDE, Firefox and Desktop settings to a module on your hdrive. I do this manually, simply bec I haven't taken the time to make this into a script for routine use. However, this is just one way that will reliably preserve settings under Slax.

Other people have their own ways-and-means and Tomas' earlier recommendation is probably the most straight-forward approach, esp if one wants to avoid typing commands or figuring how to write scripts….Jet

documented on: Apr 16, 2007, mr-roboto

I think /rootcopy is very useful for patching a live-cd among other uses but it's not a mean for persisting changes.

If used with care and from a filesystem that supports linux permissions then it is reliable. The problem arises when people uses it from a FAT filesystem. But that's a problem of the FAT filesystem not the rootcopy feature.

documented on: May 02, 2007, zariweb