This is a feature that has been on the TODO list for already more than 15 years, and finally we have it avaialble for all!
New Boot mode:
As you can see, you have now a new boot entry, if you select it, you can boot into a temporal system, this means that your system is equally the same, with your users and all, just like you left it the last time... but all the changes that you will do on this boot will be lost after your next reboot
This is perfect if you want to experiment with things and you don't want to save your changes, for example:
install suspicious software
install a lot of packages to play with them and discover new applications
run dangerous commands
doing massive changes in your system
Following the changes
What if you want to see what exactly is happening in your system? There's also a special feature for that:
When you boot your desktop, a filemanager will open pointing to a specific place that will only show the changes that will happen, for example downloading a new file or modifying existing ones, from this point you can do many things like:
seeing exactly what is being modified on your files
open the "size of directory" feature to see how much grows in size the changes you are doing
going backwards in the root tree to also see what has been modified on the rest of the OS
selecting easily the exclusive files that you want to save, for example in a USB, as the resulting work done in your tests
How to enable this feature?
Don't worry, your Elive system will be automatically updated next, including it
Do you want more fun? you can hit the power-button or even run the magic kernel hotkeys like "altgr + print + b" (don't do that in your normal system!) to force a hard, instant reboot... nothing in your system will be damaged!
This is a great feature ....... sort of like "snapshots" but then the other way round.
Not too sure if it'll really help ironing out bugs considering that my daily workhorse has lots of programs and quirks that a standard Elive doesn't have .... but still.
Lots to discover I think.
I'm wondering how this works exactly and what gets saved and what not ... i.e is 'only' the system impermutable or the user files too ........ and how this does or does-not affect my fully encrypted installs.
Heh, makes me all excited as if it's an all new shiny distro.
As a warning:
I just noticed that "impermutable mode" does not keep zsh or bash 'history'.
It would seem logical not to but if you're like me and use .zshistory as a sort-of command database or merely want to reiterate what you did before, it might bite you after a reboot into "normal mode" if you're not careful.
It also does not keep downloaded/created files or any changes which is actually a feature but does have its downsides.
Personally I think I would like some sort of "flag", like a color scheme (like some distros did if one used X11 as root) to mark that you're in "impermutable mode"... or the way QubesOs does to mark trusted and untrusted windows.
At the least a way of finding out if i.e you've left the machine running for a while (like days or weeks) and forgot in what mode its running. Thus risking a lot of data loss.
Not really in a hurry just that I've waited to "repair" anything in case you wanted to know specifics or needed logs.
Apparently you've seen the issue ..... do you want any tests done or shall I just upgrade?
As an addition: I cannot access the system files either not as the user nor as sudo.
Definitively the issue happens when the root partition is encrypted only (not tested with extra partitions like /home or similar), the issue seems to be in the tool that manages this feature itself (bilibop), im sending an email to the author now to report the issue, for now I have disabled the feature from elive-upgrader, so affected users should:
If you suffered from an unusable normal boot (encrypted installations), the solution is simple:
reboot your computer, press the "e" key while the normal boot is preselected
edit the boot parameters: search the words "quiet splash" and add after it the word "nolockfs"
back in your desktop, run the command "apug"
reboot, your system should be fixed now and included this amazing feature!
Yes, it was just a word of warning for others.
Like if I'm testing something I always do that via the command-line and if possible look back to see exactly what I did and how in my 'history'... a backlog, so to speak.
The solution is to make a copy of the backlog and post it to another machine or server before logging out and rebooting.
Nah, basically it calls elive-wallpaper-set which with the last update it actually SET the wallpaper too in E16 (before, it just added it on your backgrounds list), so basically the impermutable mode calls this command to switch to it
Let's see what is happening, you should have an entry here:
grep lockfs ~/.e16/startup-applications.list
Then rebooting when in Impermutable, that entry should be run which will show you a notification message and also change the wallpaper, if not, then:
the "lockfs-notify" command is not run
it is not updated including the wallpaper changes
the wallpaper changing doesn't works for you
I just tried again with the last updates and it works on my side, you can try to debug what is happening with the tool, see also that you have the wallpaper code:
Yes it will work when you're using the default wallpaper .... but if you use/set your own wallpaper it stays there. (and that is actually a good choice IMO)
I've noticed that a few years ago when I was making E16 themes.
Anyway the wallpaper change (or not) is totally unimportant if there's a notification to be had elsewhere...simple as that.
The notification always worked, thats why im thinking that maybe you didn't had it well installed, check the previous details to find the issue
And about the wallpaper no, it should work even if you have a custom wallpaper configured, its a direct E call to set the wallpaper and that's the purpose of elive-wallpaper-set which should work no matter what (for example when a user right click in an image and "set wallpaper", or in impermutable which should change it, so its also a temporal state of your system which will be deleted later), if doesn't works, then is a bug in E that should be reported