请有兴趣同志翻译一下这篇文档，来自slax的论坛，很有用。

Howto resize slaxsave.dat 

I have slax standard edition installed on a fat32 partition on my hard disk. I start it using the linux.bat / loadlin.exe as found in the /boot/dos directory.
I had previously setup a 512Mb slaxsave.dat and, as it worked very well and reliably, I decided that a bigger one would be useful. But, I had already made lots of changes and really didn't want to lose any data. Changing over to a 1Gb slaxsave.dat wasn't as easy as expected, and in the process I learned a lot about how slax works, even though I don't understand it all, or even at all!
So this is a guide for others to follow.

We don't want to overwrite our original slaxsave.dat by the new unzipped file, so RENAME it first!!!
Now let us get down to business.

First of all, the zip files of the variously sized slaxsave.dat's may be corrupt, or perhaps they just don't like being extracted by Windows' Winzip. Whatever, the 1Gb size didn't work for me. After unzipping, I found it was necessary to test them first. This is done by mounting them using slax with a sequence of commands something like this...

mkdir /mnt/temp1
mkdir /mnt/temp2
mount -t xfs /mnt/hda1/slaxsave.dat /mnt/temp1 -o loop

The first two lines prepare extra mount points for our use. The mount command is straightforward enough, but we are interested in the result. You would have to "dmesg | tail" to see the results after an error.

Possibility one. No message occurs after the mount command, you just get a new prompt.
Meaning - slaxsave.dat is good and NOT mounted at startup.

Possibility two. Message reads...
XFS:Filesystem loop27 has duplicate UUID - can't mount
Meaning - slaxsave.dat has already been mounted by the system and is in use.

Possibility three. Long error message from mount. Dmesg | tail gives...
XFS: bad magic number
XFS: SB validate failed
Meaning - slaxsave.dat is corrupt.

Let us consider possibility three first. You have to make a new filesystem on it first. cd to /sbin, then "mkfs.xfs /mnt/hda1/slaxsave.dat". You'll get a lot of lines afterwards which you probably wont understand. Nevermind, just try to mount it again as above. Now you should get no error message - i.e. possibility one. If this doesn't work, ditch it and start again.

Now possibility two tells us that we can't work on this file when it is in use. OK, I can live with that!

Possibility one is the confusing aspect. Why isn't it used by the system? From what I have read on this forum, a slaxsave.dat will automatically be found by slax. NOT so! It needs the "changes=/mnt/hda1/slaxsave.dat". Even more confusing is the fact, verified by experiment, that slaxsave.dat cannot be on the same partition as the slax system. (My system is on hda5)

OK, now we have two files; let us avoid all confusion and rename both files - original and new slaxsave.dat's - to something ridiculous, and move them to a different partition if necessary. Edit /boot/dos/config to remove any "changes=" so that next we can fire-up slax WITHOUT any slaxsave.dat

Oh, more confusion! No slaxsave.dat should mean not enough memory available. (I only have 256Mb RAM) But no, slax has found some extra space somewhere according to "df -h". Where the hell did that come from?
Whatever, to save memory, we wont "startx" since the GUI isn't necessary.
Remember, you have to make the mountpoints again - mkdir /mnt/temp1 and 2 as before.
Now mount both slaxsave.dat's (remember - they should have your ridiculous names) on /mnt/temp1 and /mnt/temp2. Get the order correct! Original first, then new one.
Mounted OK?
Copy the original to the new one.
cd /mnt/temp1
cp -dpR * /mnt/temp2

At least two warning messages appear but ignore them - a warning isn't an error!

All OK? Do a "df -h" and you should now see both temp1 and temp2 listed. Hey! The files aren't the same "Used" figure! Surely they should be if they are identical??? Apparently NOT - and I don't understand this either but just accept it.

Fine! umount both and then edit 'config' to include "changes=/mnt/hda1/ridiculous.shit" or just rename the new file to slaxsave.dat again if you so wish.

Strange, it doesn't seem to matter if you use /dev/hda1 or /mnt/hda1 in the "changes=" line. I guess the partition is already mounted anyway before this line takes effect.

Reboot with your fingers crossed.
Hopefully, your new slaxsave.dat is fully functional.

I expect many more experienced readers will ask "Why not just use the live, working system to copy the data to just one mounted slaxsave.new

slaxsave.dat must be mounted somewhere! Yes, it's in /mnt/live/memory and it consists of three folders - changes, images and modules.

In theory, from /mnt/live/memory you should be able to...
cp -dpR * /mnt/temp1

I tried it and it didn't work! I really don't know why.

Anyway, I got it working eventually as you have seen.
Probably many readers don't know how to use slax on a harddisk so I'll include a little extra stuff here.

Copy everything from the slax CD to a folder named 'slax' or 'popcorn' or 'killbill" - your choice!
Then find the /boot/dos folder inside and edit "config".

Any required cheatcodes are placed on the first line after ../vmlinuz WITHOUT the word slax!
e.g. ../vmlinuz changes=/mnt/hda1/slaxsave.dat

Add a new line at the end...
from=/dev/hda5/slax
(change the disk partition as needed and your chosen foldername!)

Now you can start from DOS by cd'ing to the \slax\boot\dos directory and typing "linux" - just remember to use the Windows/DOS slashes! Stuck on Windows? Press F8 repeatedly as your computer starts until the boot menu appears, then choose 'safe mode command prompt'

I hope this helps to make slax more enjoyable for you.