Direct-save to working-partition fixed

This is very good news, as since changing from aufs to overlay it has been broken. I posted about the fix for mounting overlay, that has now resulted in direct-save working:

• Fix for fscrypt folder on rw layer in overlayfs — October 18, 2025

The default is that the current session runs in RAM, and you flush it to permanent storage whenever desired, usually at shutdown. There is a "save" icon on the desktop, so that you can save whenever you desire, but notice also that it has a checkbox:

If the checkbox is ticked, then at next bootup there is no longer any need to save, as writes are direct to the working-partition. There is still a "save" icon on the desktop, and clicking it brings up this:

To implement this, though, has required a structural change. The working partition has folder /mnt/wkg/.session, which is where the session gets saved. However, in the next release of EasyOS, the session will be saved to /mnt/wkg/.session/session1, that is, a sub-folder inside .session.

I have put a hack in the initrd, in script /inc/04next-boot-kb-pw, that detects if there is an updated from Easy 7.0.20 or earlier, and moves everything from .session into .session/session1

However, that is a problem, as cannot rollback to 7.0.20 or earlier. Or rather, can, but everything will be in the wrong folder, so you won't have installed packages, browser history, etc. But, everything saved in containers is OK.

If you do need to perform a rollback to 7.0.20, it will require a manual fix. A quick hack would be (do this running a different EasyOS:

# cp -a -f /mnt/${WKG_DEV}/${WKG_DIR}.session/session1/* /mnt/${WKG_DEV}/${WKG_DIR}
.session/

...then delete /mnt/${WKG_DEV}/${WKG_DIR}.session/session1

I will try to fit in a lot of testing tomorrow, so that the next release will be verified to work well and no rollback will be required, hopefully.     

Tags: easy