Porteus

See also: Stuck on v5x64 Xfce persistence (Post by sean #93431) under Intermediate/Advanced User Questions

I made 2 Porteus 5.0 Flash-Drives from indentical brand & size. One I made by extracting the .ISO and copying the contents to a FAT32 partition on said Flash-Drive. On the initial boot I used the Porteus SaveFile Manager to make a save.dat file. When Porteus SaveFile Manager ended processing it opened /porteus/porteus-v5.0-x86_64.cfg asking me to confirm the changes=/path/to-the-file/save.dat.

This had to be done to satisfy instructions on the boot screen in order for persistence to work. A visual "change" was made to the Panel.

Subsequent boots showed persistence did not work, however one can observe Porteus "searching for porteus-v5.0-x86_64.cfg" during the boot process.

I then made the 2nd Porteus 5.0 Flash-Drive. This time I booted Porteus from a DVD, then ran the Porteus Installer for the installation to the Flash-Drive. This drive was also formatted to FAT32. When the installation completed I booted the Flash-Drive and ran the Porteus SaveFile Manager so as to create the necessary save.dat file for persistence. When Porteus SaveFile Manager completed it's processing I was again presented with a file for establishing the correct changes=/path/to/save.dat. This file, /boot/syslinux/porteus.cfg was much larger than the one on the other drive. I made the requested edit to the file and saved it. I again made a visual change to the Panel.

Subsequent boots showed persistence was now working with this Flash-Drive. However one can observe Porteus "searching for porteus-v5.0-x86_64.cfg" during the boot process. When, obviously, it is using /porteus/porteus.cfg for the persistence.

During the 1st of the 1st Flash-Drive installation Porteus SaveFile Manager offered the in-correct configuration file for editing. On the 1st boot of the 2nd Flash-Drive installation Porteus SaveFile Manager offered the correct configuration file for editing.

A confusing state of affairs which I'd consider a "bug" ;-) First one I ever found with no legs or wings!

Sean

This posting relates to the problem: Stuck on v5x64 Xfce persistence (Post by Ed_P #93442)

hi Ed_P but when you have done the save.dat container the user have mount in loop for check it,if is ok.

This what I got when it finished beny.

root@porteus:/home/guest# mount -o loop '/mnt/live/porteussave.dat' /mnt/loop
Ed_P the container is mounted without error so i have done this on ext4 system and the container is ext4 too

hi Ed_P so when you make the save.dat,i have done in this way you have to build the save.dat on the root of the key or what you use for the boot the system i have mine in changes=/mnt/sdh1/save.dat this line is added to the porteus.cfg after this you have to add the line also in the /boot/porteus.cfg i have choose the txt mode,when you boot system there is a save.dat check first and after this step the load of the modules and all the tweak you have done are all in tested,so if you want to do in other way you are free to open bug report.

I am aware how the /boot/syslinux/porteus.cfg file works beny. My top 2 entries: And in my /porteus/porteus-v5.0-x86_64.cfg file nothing but # lines.

when save.dat is build you have a report that tell you ok you have done now i write the changes=where you have choose in porteus cfg and you have to add to the boot options in /boot directory and i think the append line is a bit strange,you are shure for the uuid and changes line... too complicated i don't have fat32 but with ext4 work

You saw what msg I got posted above.

what that you don't have the write permission? i have choose the sd root for this question i have used for the kernel build and also for the save.dat because is ok for the heavy work