General Debian • Re: Immutable Bookworm

Code:

sudo rsync -axHAXS --progress --exclude=/tmp/ --ignore-errors --delete /run/live/overlay/rw/ /extra0/rw

Code:

sudo rsync -axHAXS --progress /extra0/rw/  /run/live/overlay/rw/ 

In practice, we always exclude google chrome cache and config files from persistence:
The second exclude=google-chrome/ parameter will exclude both ~/.config/google-chrome and ~/.cache/google-chrome folders from retained persistence. This is one of the advantages that a "portable" (for lack of a better word) persistence is better than using a fixed persistence partition. If not managed properly, these folders can grow to multiple gigabytes. But more important, some of our older male students only trust using their immutable system to watch internet porns lest it be found out by their kids. This is the main reason that keeps them from using Windows or Apple. Keeping google caches in persistence would defeat this purpose.

Using "portable" persistences (again for lack of a better term) has other advantages. For example, as a GNOME user, I always wanted to try KDE/Plasma. After booting from the immutable Sid (or Bookworm), I can easily do the requisite apt install and switch the DE from GNOME to KDE (or any other DE), then save the /run/live/overlay/rw folder as /extra0/rw.KDE or something like that. Next time when I want to see how much KDE has improved, I can simply rsync the rw.KDE folder to the RAM or to the fixed persistence partition. But, as our older but wiser students manifested, the biggest advantage is the peace of mind. Especially when using Sid.

Statistics: Posted by pwzhangzz — 2024-09-09 18:14

---