changes not saved on EXIT or by dump-session

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
Post Reply
rych
Samurai
Samurai
Posts: 196
Joined: 04 Jan 2014, 04:27
Distribution: Porteus 4.0 64 LXDE
Location: NZ

changes not saved on EXIT or by dump-session

Post#1 by rych » 30 Apr 2021, 10:26

In Porteus 4.0 x64, when I manually activate a module and invoke the app, I can see its folder with the changes appearing in the live folder tree. However, those changes are not reflected in the changes sub-folder on the USB. I can stop and deactivate the module -- the changes sub-tree remains mounted in live file system.

That's to be expected because I actually boot with "changes=EXIT:/porteus/". Unfortunately, neither running the dump-session, nor actually rebooting saves the changes. The normal changes=/porteus/ cheatcode works fine.

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 2962
Joined: 20 Mar 2012, 03:42
Distribution: 5.0rc1-64bit all-DE+more
Location: australia
Contact:

changes not saved on EXIT or by dump-session

Post#2 by ncmprhnsbl » 30 Apr 2021, 12:05

i could be completely wrong, but .. maybe, try "changes=EXIT:/dev/<your device>/porteus/" or even "changes=EXIT:/dev/<your device>/porteus/<name of changes folder>" ie. full path
somebody who actually uses change=EXIT: , might have a better idea..

.. what does cat /mnt/live/tmp/changes-exit give?
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
Ed_P
Contributor
Contributor
Posts: 6108
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 4.0 & 5.0rc3 ISOs
Location: Western NY, USA

changes not saved on EXIT or by dump-session

Post#3 by Ed_P » 30 Apr 2021, 15:45

Another file to check would be the changes-exit.conf file to see if it may be impacting your changes.

It's possible that the changes file only saves changes made to modules present when booting. Which from a changes file space point of view is a valid approach. Why save changes to folders which may never be used again.

So, you could create a module of your changes which you activate after you activate the module in question or you recreate the module you're using with your changes added to it.
Ed

rych
Samurai
Samurai
Posts: 196
Joined: 04 Jan 2014, 04:27
Distribution: Porteus 4.0 64 LXDE
Location: NZ

changes not saved on EXIT or by dump-session

Post#4 by rych » 01 May 2021, 06:16

Code: Select all

root@porteus:~# dump-session 
syncing what's left in buffers
saving changes to /mnt/sdb2//porteus/ - this may take a while...
find: `bin': No such file or directory
find: `lib': No such file or directory
find: `lib64': No such file or directory
find: `opt': No such file or directory
find: `sbin': No such file or directory
sed: -e expression #4, char 1: unknown command: `_'
sed: -e expression #4, char 1: unknown command: `_'
sed: -e expression #4, char 1: unknown command: `_'
sed: -e expression #4, char 1: unknown command: `_'
sed: -e expression #4, char 1: unknown command: `_'
sed: -e expression #4, char 1: unknown command: `_'
find: `bin': No such file or directory
find: `lib': No such file or directory
find: `lib64': No such file or directory
find: `opt': No such file or directory
find: `sbin': No such file or directory
session saved
root@porteus:~# cat /mnt/live/tmp/changes-exit 
/mnt/sdb2//porteus/

Code: Select all

root@porteus:~# cat /etc/changes-exit.conf
# Folders listed in this config file will be saved during reboot and shutdown when 'changes=EXIT:' cheatcode is used.
# Folders starting with '!' are omitted. This is useful if you want to save whole folder except for particular subfolder(s).
# An example is inclued in default config below: Porteus will save whole /var folder except for /var/run and /var/tmp subfolders.
# Other example: "!/home/guest/.mozilla/firefox/c3pp43bg.default/Cache" will skip saving of Firefox caches from guest account.
# Thanks to Rava for suggesting implementation of '!' exceptions.

/bin
/etc
/home
/lib
/lib64
/opt
/root
/sbin
/usr
/var
!/var/run
!/var/tmp
Indeed my folders were not listed in the changes-exit.conf as they are in unusual places -- adding them to this file seems to have solved the problem.Thank you Ed_P, and ncmprhnsbl

Post Reply