saving changes

Prev		Next

http://www.slax.org/forum/viewtopic.php?t=17717

before explaining my problem, i think one thing is obvious: too little information on the website, and a lot of separate informations on the forum (sometimes confusing, as in every forum).

so, as far as i could gather them: config.lmz; slaxconf.mo; slaxsave.dat… it seemed to me that slaxsave.dat is the one to use if you don't want to bother with typing commands everytime you boot and log off;

so i extracted the save128.zip, put in on my usb stick, added changes=/slaxsave.dat to grub's menu.lst; didn't work;

then found on a topic that it's better to put it on a slax/ directory on the stick: didn't do any good…

Vector

saving changes

> i think one thing is obvious: too little information on the website, and a
> lot of separate informations on the forum (sometimes confusing, as in every
> forum).

Couldn't agree more!

When doing changes saving configuration, I always reboot 3 times to verify.

boot my USB Slax to make the modification.
boot my USB Slax again, and do the following in root's home dir.
```
echo abc > abc
```
then reboot the 3rd time to verify that the abc file is there and the content is kept.

Have you tried reboot enough time?

PS.

It doesn't matter whether changes=/slaxsave.dat or changes=/slax/slaxsave.dat

just make sure the file is there!

documented on: 2007.06.02, xpt

saving changes

	it works just fine now, with the file provided : slax128.zip it just didn't work when created with dd if=/dev/zero of=slaxsave.dat bs=1k count=20k (seen somewhere in the forum)
	-- Vector

Just for the archive, you miss the 2nd step, which is the most important one.

xpt

saving changes

> > Just for the archive, you miss the 2nd step, which is the most important
> > one.
>
> mke2fs slaxsave.dat, you mean?

FWIW, Tomas suggested and used mkfs.xfs as the filesystem for it.

documented on: 2007-06-05, bb as guest

saving changes

	ok, everything alright then. Whistle
	-- Vector

Not really — that 20k count produces a 20mb save file — not large enough to be useful at all, could easily fail on the first attempt to use it. Even 128 and 256mb are not enough if you expect it to also hold downloaded modules.

I suggest that anyone using a slaxsave.dat file should periodically boot without it, then loop mount it to examine what you are actually saving — it might surprise you what's in there. The save function will definitely fail when it gets full.

documented on: 2007-06-05, bb as guest

saving changes

	Actually a ~20mb save file is the maximum I can afford — small USB. Are all changes goes into the file; i.e., is there any exception, e.g., /tmp that I can safely use?
	-- xpt

for a 20mb space, configsave is the only useful option — you'll just have to remember to run it after every significant change, and even then you'll have to modify your standard practice — for example, clearing the Firefox cache and /tmp before saving. That FF cache alone can get to 50mb size.

Linux filesystems tend to be very messy, lots of additional copies of things, immense numbers of 0-length files, empty directories, etc. I'm not prepared to rewrite linux, so we just have to work with it.

documented on: 2007-06-07, bb as guest