Ed_P wrote:An interesting approach fulalas.
I thought this was the most common way of using Porteus
Ed_P wrote:What creates the /rootcopy/etc folders and files? Just using rootcopy? My flash drive's /porteus/rootcopy/ folder is empty.
You need to copy (manually or through a script) everything you want to keep/save from system folders to /mnt/usbstick/porteus/rootcopy folder, then during the boot Porteus will copy everything back to the corresponding folders. For example: I changed some settings of SMPlayer (video player), but I want to keep these settings let's say forever (no need to be always changing them), so I manually copied /home/guest/.config/smplayer/smplayer.ini to mnt/usbstick/porteus/rootcopy/home/guest/.config/smplayer/ . Every time Porteus boots, it makes a copy of this file back to /home/guest/.config/smplayer . But, as I said before, somethings are constantly changing and I want to save them every reboot/shutdown, so I use rc.local_shutdown script.
Ed_P wrote:It should be noted that the non-rootcopy's rc.local_shutdown file needs to be made executable for it to run. At least mine did in 3.2.2 Cinnamon 64-bit. And in doing so it checks the space usage of a save.dat file when shutting down.
I didn't have to do anything, just changed rc.local_shutdown script and put it inside /mnt/usbstick/porteus/rootcopy/etc/rc.d/
donald wrote:There is no significant increase of "speed" with copy2ram
If one does not want to pull/plug out the boot device copy2ram is superfluous.
AFAIK, copy2ram has two advantages:
1- you can unplug your USB stick after boot
2- all modules inside
base and
modules folders you try to execute are already loaded in RAM, so they open instantly
So, regarding performance, you're right: copy2ram only moves loading time from modules execution (under demand) to boot.