Save.dat container (SOLVED)

[tome]

EdP, see Bug reports (fist topic) if you want use ntfs

[Ed_P]

Thanks @tome. Awkward for me to fix since I boot the ISO directly. Will have to think about editing files in the ISO.

Thanks again for responding.

[tome]

or unpack vmlinuz, initrd.xz and use from=/.../...iso

[Ed_P]

Another thought, rather than change the ISO can't I change the script from within the system I am running? Where would I find it? And do I need to be root to change it?


Found. /mnt/live but can't update as guest.

Ha Hah!! Logged off of guest and onto root, pulled up the file and applied the change noted in the bug fix, Tada I have shutdown and rebooted and my passwords were reapplied. The ntfs savefile fix is in the savefile.dat file. Perfect!!

[budchekov]

Have you gotten the save changes to work yet?

Nope, someone should lock this thread.

[Ed_P]

Have you gotten the save changes to work yet?

Nope, someone should lock this thread.

Hey!! I'm using it for my save file situation.

Ok, back to your problem. You created a save file on your USB drive. Is the drive formated as FAT32 or a Linux format? What is the path to your file? Have you tried putting it in the root of the USB drive?

[budchekov]

Ok, back to your problem.

Thanks Ed, but it's no longer a problem, uninstalled and moved on.

[tome]

EdP I'm not sure but you are wrong, you can not save /mnt/live to changes, every time after reboot you will still need update /mnt/live if you want save changes, but maybe you use some tricks.

[Ed_P]

EdP I'm not sure but you are wrong, you can not save /mnt/live to changes, every time after reboot you will still need update /mnt/live if you want save changes, but maybe you use some tricks.

Well I just rebooted from using Windows and my Porteus reconnected to my WiFi and had the password without my needing to enter it. The change in the cleanup file allowed my changes to be saved.

Oh!! I see what you are saying. The info for the file shows the original file date rather than today's. So the fix has to be reentered each boot.

hmmmm Patch file, create a backup, restore backup each boot. Sounds reasonable but I have limited scripting skills.....

Thanks Ed, but it's no longer a problem, uninstalled and moved on.

Oh, ok. I thought you were a tech.

[tome]

replace your initrd.xz with updated from:https://www.dropbox.com/sh/ui4ydoh3j34xkoy/awngRHBa80 - Porteus folder, and change name of this file or change path in your bootloader.

[Ed_P]

replace your initrd.xz with updated from:https://www.dropbox.com/sh/ui4ydoh3j34xkoy/awngRHBa80 - Porteus folder, and change name of this file or change path in your bootloader.

Thank you @tome. An interesting option.

At present I have found that this series of commands works for me also:

Code: Select all

  guest@porteus:~$ su
  Password: toor
  root@porteus:/home/guest# cp -a /home/guest/cleanup /mnt/live/

[phhpro]

Not sure if this is of any interest anymore. Just came across this one on the Puppy board:

Pelo wrote:
I have Porteus on an USB stick. It's a fine distro. But i never understood how to save sessions. I use Porteus to access easily to KDE apps.
I m going to see this version 2.1.

Ted Dog wrote:
Yes I wish porteus explained howto better, I've never got that working.

I had problems with the Porteus SAVE FILE TOOL too. Although it seemed simple enough, the created file never seemed to actually get saved. The problem seems to be with SYNCing the generated SAVEFILE.dat in RAM to actually write it to the USB flash drive.

For those having the same problem, there is a workaround until the SYNC fix comes out:
Quote:
Use the SAVEFILE MANAGEMENT menu to create the file. I used the EXT4 option and chose the location to be the internal distro's root directory. It then creates the file (in RAM).

Next, from the SAVEFILE menu, select the REPAIR option, not to repair it but just to grab the file (from RAM) and copy it to FILE MANAGER (to your preferred location on the USB flash drive). I copied mine to my /multiboot/porteus/ directory. I then added this option to my porteus-rw.cfg file's APPEND line:

changes=/multiboot/porteus/SAVEFILE.dat

After that, persistence worked fine after rebooting.

The complete thread is here:
http://www.murga-linux.com/puppy/viewtopic.php?t=87940

Jump to page 3, towards the bottom to find the above cite.

[fanthom]

@phhpro
yes - syncing was probably the issue and brokenman added already a 'sync' command after every 'dd' in save file manager tool.

[Ed_P]

Kind of a related question, we use the cheatcode to save our changes but do the changes get used/read if we don't use the cheatcode to save them? And if not is there a way to do that?

[francois]

There is nothing going on if you do not use the changes cheatcode: nil, néant, zéro, or if you prefer it corresponds to always fresh. You do not have access to previous data unless it has been caught in some way into a module. Changes have the life of the session.

What do you want to do? The question is not clear to me.