Porteus

root@porteus:/home/guest# save-changes

save-changes /path/to/resulting/module.xzm

You must give a path to save your changes to.

• Start with barebones xfce
• Set up all apps etc.

• Code: Select all

  save-changes initialization_module.xzm

• Store in modules folder
• Bear in mind contents of save.dat could overwrite initialization_module setup
• Use boot parameter (cheatcode) cliexec=activate~/mnt/sdXy/porteus/optional/initialization_module.xzm if you always wish to start off with these settings (module placed in optional folder).

Bogomips wrote:Probably need

Code: Select all

root@porteus:/home/guest# save-changes

save-changes /path/to/resulting/module.xzm

You must give a path to save your changes to.

find /mnt/live/memory/changes  -iname "*" -mmin - 2

#!/bin/bash

# Save 3.2 changes as a mod file 

# Color definitions
txtbld=$(tput bold)               # Bold
txtred=${txtbld}$(tput setaf 1)   # Red
rst=$(tput sgr0)                  # Reset

function redpswd() {
  echo -e "$1" $txtred  
}

if [ `whoami` != "root" ]; then
    redpswd "Enter root's password"
    su -c "sh $0 $1"
    exit
fi
echo $rst

if [ "$1" == "x" ]; then
   echo 'find /mnt/live/memory/changes  -iname "*" -mmin -3'
   find /mnt/live/memory/changes  -iname "*" -mmin -3
   echo
   exit
fi

if [ -d /tmp/mod/ ]; then
   rm -rf /tmp/mod
fi
mkdir -p /tmp/mod

# copy modified files
cp -a --parents    /home/guest/.config/nemo/*                     /tmp/mod/
cp -a --parents    /home/guest/.config/gtk-3.0/*                  /tmp/mod/
cp -a --parents    /home/guest/.config/dconf/*                    /tmp/mod/
cp -a --parents    /home/guest/.cache/dconf/*                     /tmp/mod/
cp -a --parents    /home/guest/*                                  /tmp/mod/

cp -a --parents    /home/guest/.mozilla/firefox/profiles.ini      /tmp/mod/
cp -a --parents    /home/guest/.mozilla/firefox/dxsqumip.default/places.sqlite  /tmp/mod/
cp -a --parents    /home/guest/.mozilla/firefox/dxsqumip.default/prefs.js       /tmp/mod/

cp -a --parents    /home/guest/.cinnamon/configs/panel-launchers@cinnamon.org/* /tmp/mod/
cp -a --parents    /home/guest/.cinnamon/configs/power@cinnamon.org/*           /tmp/mod/

cp -a --parents    /etc/NetworkManager/system-connections/*       /tmp/mod/
cp -a --parents    /var/lib/dhcpcd/*                              /tmp/mod/
cp -a --parents    /var/run/NetworkManager/*                      /tmp/mod/

cp -a --parents    /usr/share/applications/cups*                  /tmp/mod/
cp -a --parents    /usr/share/applications/*print*                /tmp/mod/

cp -a --parents    /etc/usm/*                                     /tmp/mod/
cp -a --parents    /var/usm/                                      /tmp/mod/

du -h /tmp/mod/

echo
echo Press Enter to create module, Ctrl+C to end.
read

dir2xzm /tmp/mod /tmp/mychanges.xzm   &&   rm -rf /tmp/mod

echo 
ls -sh  /tmp/*.xzm
read

Bogomips wrote:@ Ed_P you probably want:

Code: Select all

root@porteus:/home/guest# changes-time

Ed_P wrote:If you make a change then run the app it includes everything that was changed in the past 3 minutes but maybe you only needed the last 1 minute.

root@porteus:/home/guest# changes-time

Use this script save Porteus changes made in definied time period.
Enter time interval or press enter for keeping default value (3 minutes):
0

• Save change at point A
• Save changes at point B.
• Compare directories.
• Make script to get the difference. Should be quite a challenge for Programming Section:

  Code: Select all

  sudo save-changes ch_a.xzm
  # Do some processing to generate required changes
  sudo save-changes ch_b.xzm
  mkdir a b
  sudo mount ch_a.xzm  a
  sudo mount ch_b.xzm  b
  diff  -qr  b  a
  # Rest of script to get Difference
  ...
  

Bogomips wrote:

Ed_P wrote:If you make a change then run the app it includes everything that was changed in the past 3 minutes but maybe you only needed the last 1 minute.

Code: Select all

root@porteus:/home/guest# changes-time

Use this script save Porteus changes made in definied time period.
Enter time interval or press enter for keeping default value (3 minutes):
0

Or if undesirable to be time bound:

• Save change at point A
• Save changes at point B.
• Compare directories.
• Make script to get the difference. Should be quite a challenge for Programming Section:

  Code: Select all

  sudo save-changes ch_a.xzm
  # Do some processing to generate required changes
  sudo save-changes ch_b.xzm
  mkdir a b
  sudo mount ch_a.xzm  a
  sudo mount ch_b.xzm  b
  diff  -qr  b  a
  # Rest of script to get Difference
  ...
  

Bogomips wrote:

• Use boot parameter (cheatcode) cliexec=activate~/mnt/sdXy/porteus/optional/initialization_module.xzm if you always wish to start off with these settings (module placed in optional folder).

FURRY_NOVA wrote:Is there any proper Porteus application data backup solution? I've been researching since I don't wanna keep making a new dat container and personalizing all the applications over and over again each update. I've found that folders with . prefix in guest directory have the stuff. But I thought I ask here to make sure since I don't pointlessly pass previous Porteus version problems on to the new container.

port wrote:

Bogomips wrote:what's the difference of doing that (save module in optional folder and run activate via cliexec kernel parameter) and simply put the module in modules folder (which is loaded automatically at boot time)?

Ed_P wrote:What I do, periodically, is copy my porteussave.dat file to another folder, rename it porteussave.dat.xzm and load it as a module either when I boot or when I want via an activate.

brokenman wrote:For more control over saved folders please look at 'magic folders' in Porteus Settings Centre.

IMPORTANT NOTE:
If invoking save-changes directly from a terminal please be aware that you need to supply a 'real file system' for the target backup. You can't create the resulting module anywhere on the live file system (e.g. /tmp /home)

It essentially just packs everything in the changes folder into a module.