-- About transforming large pupsaves
into sfs archives approximately 2/3 smaller --
(Please read everything in this post before you proceed.)
Let's say, for the sake of argument, that we have a huge 2.5Gb pupsave
named slimsave_bodelibop.3fs, which is half full, in our slim 6 directory.
~~~~~~~~~~~
If you may be interested in slim6, a fine slacko-6 derivative, it is here:
Slim6:
http://archive.org/download/Puppy_Linux ... slim-6.iso
Thread:
http://murga-linux.com/puppy/viewtopic. ... 446#885257
~~~~~~~~~~~
Back to our situation --
Sadly, we cannot keep our pupsave as it is, we need to free some space
on our thumb drive.
First we back everything up. Yes, everything. We do not want to be
caught up a certain creek without a paddle. Understood? (Rule no 1 of
computing, my friends, on any OS, is: back up, back up, back up.) The
easiest way may be to back-up the whole directory.
We open a console in the dir. where the bodelibop pupsave is located.
We make a back-up of the main globicons file, like so:
Code: Select all
cp -f /root/.config/rox.sourceforge.net/ROX-Filer/globicons /root/.config/rox.sourceforge.net/ROX-Filer/globicons.bckp
We type (if you're smart, you'll copy each line, after highlighting it, with
Ctrl-C and then paste it in the console with a middle click of your mouse):
Code: Select all
mount -t ext3 -o loop slimsave_bodelibop.3fs /mnt/zip
/mnt/zip exists in all Puppies, and it is never used. So it is safe to populate it.
(It is a relic from the time of the physical ZIP drives. Remember those?)
If your PC does not have much RAM, it may be safer to change the above
one-liner to:
Code: Select all
mkdir /mnt/home/bodelibop;mount -t ext3 -o loop slimsave_bodelibop.3fs /mnt/home/bedelibop
Once that is done, still in our console, we type:
Code: Select all
mksquashfs /mnt/zip/ bodelibop.sfs -noappend -all-root -b 1048576 -comp xz -Xdict-size 100%
If you are using the alternative directory at /mnt/home/bedelibop/,
this one-liner becomes:
Code: Select all
mksquashfs /mnt/home/bodelibop/ bodelibop.sfs -noappend -all-root -b 1048576 -comp xz -Xdict-size 100%
It takes a couple of minutes. The resulting sfs should be around 400 Mb,
~ 1/6th of its original size.
Now we don't close that console right away... We check if we have the
bodelibop.sfs archive, by typing:
If we do, we type:
to unmount the zip directory, we do not need it anymore. Or
if you used this other mount point.
We do not erase that bodelibop pupsave file just yet. We need a new
pupsave file to replace the one we will not be using anymore, say of 192
Mb, to be comfortable. So...
we download the attached,
unzip it it in your Puppy directory,
make it executable -- by typing
and run it -- by typing
This creates a pupsave named "arf" in the current directory, with the
proper prefix (indicating your current Pup).
Now we exit this console and reboot the current Pup.
Important -- Upon reboot, choose the new pupsave, the one with
"arf" in the name, NOT your old bodelibop one.
You should now be back in your Pup.
If your desktop icons look funny, open a console and run line 22 of the
psave script. I.e.:
Code: Select all
gdk-pixbuf-query-loaders --update-cache
If some other details of your desktop seem jumbled, or the time on the
taskbar clock is wrong, do not try to fix them at this point: it is because
your new sfs file has not been loaded yet. So...
Still from that console, we type:
and mount the bodelibop.sfs from the drop-down list on the left. sfs_load
will ask you if you wish to run one of the executables in bodelibop.sfs. At
this point, it may be best to answer "no" and to exit sfs_load.
Now we reboot again, and this time, all the content of our former
bodelibop pupsave should be available. Now is the moment to adjust
details on your desktop, if any need adjusting. Also, if some icons are still
looking funny on your desktop, type:
Code: Select all
cp -f /root/.config/rox.sourceforge.net/ROX-Filer/globicons.bckp /root/.config/rox.sourceforge.net/ROX-Filer/globicons
You may have to type Ctrl-Alt-BackSpace and then
to get all the icons to appear correctly. (To restart X, in other words.)
Then try out all the executables that you used in your old pupsave, to be
sure. Try to be thorough. Once you are
quite sure (I repeat:
quite sure)
that everything is ok, you may erase your old bodelibop.3fs pupsave. (Or
zip it and keep it as reference.)
~~~~~~~~~~~
Try the above procedure. Nothing bad can happen, you have made back-
ups (right?) that you can use if you need to revert to the previous state.
I'll be watching for your comments and even mouthfuls!!!
TWYL.
~~~~~~~~~~~
PS. -- I made the above pseudo-code tutorial long and tedious on
purpose. Besides developing, Puppy developers have the moral duty
of combating laziness in users.