Let's say one wants to copy a customized Porteus 3.1 from his key to another (copy, friend's or any case)
Particularily a user's $HOME that is nice and all, and some added/built modules.
Same case if a user wants to push some changes he did on e.g. test-stick to his spouse-stick.
From http://www.porteus.org/tutorials/19-recovery.html
Well I tried that and `mloop /path/to/present/changes.dat` mounts to /mnt/loop (all fine till that point). Which is 100% empty.To access the files in a .dat file container, you can use the mloop command, e.g.:oldsave.dat container will be mounted at /mnt/loop/ and you can copy your files from that location to another temporary location, such as /tmp/oldsave/, then unmount the old container:Code: Select all
mloop /mnt/sdb1/porteus/oldsave.dat
Code: Select all
uloop
On the opposite, `mloop /other/stick/path/to/changes.dat`mounts to /mnt/loop and shows the existing porteus files saved on that .dat.
To achieve my goal, with the destination changes.dat still mounted I
* copied/replaced the dotfiles/dirs from /home/USER to /mnt/loop/home/USER/, and
* copied the new modules to /mnt/spouse-stick/path/to/porteus/{modules,optional}, (both are Porteus-3.1-i486), eventualy replacing the older e.g. 04-firefox.xzm (v31) with the newer one (v38)
Is it OK to do like this? If closing apps like Firefox before synchronizing e.g. ~/.mozilla to the other, mounted changes.dat?
If so, shouldn't the FAQ clarifies that: if using a .dat file, it has to be unused ? And add a part like « How to copy or synchronize your changes from a running live Porteus to another changes.dat/USB stick with Porteus?
Also I tried to use the Porteus tool to enlarge a .dat file
ANd while it says "Your changes will be saved" (if I remember it well), upon editing that stick porteus.cfg to point to the new, bigger changes.dat none of my customization were preserved.
Oh and a last question.
Quoting Georges from [SOLVED] Can't Save Changes on a Live USB
All the `changes.dat` path in y porteus.cfg are relative to the *root* of the sticks e.g.George wrote:I followed these instructions and still couldn't make it to save changes. After I reboot I'm back to where I started, even though I can see the mysave.dat file in the USB root.brokenman wrote:You porteus.cfg file looks good. Your cheatcode looks good. Lets try one more time from the beginning and if changes aren't working we will move onto creating a linux file system partition if that is an option.
Please create your porteussave.dat and change the name to mysave.dat (just to remove confusion) and place it on the root of your USB device. That means on the USB device you should have the folder boot, porteus and a file called mysave.dat
Be sure that you have only one install of porteus on the USB, and that no hard drive porteus install might be getting picked up.
Here are the changes= cheatcodes you should try.
changes=/dev/sdb1/mysave.dat
changes=/mnt/sdb1/mysave.dat
changes=UUID:E8FB-6830/mysave.dat
If you see the message during boot about creating the .dat file then the changes= code did not work.
Code: Select all
changes=/multi/porteus/changes.dat
So what's the point in bothering the newbies with UUID and else exactly? Note: I've been using Porteus 3.1 on a few sticks for a couple of months, with up to a few sticks plugged in (after boot!).