You don't. It is handled by systemd. Mentioned below, drop that 'n'! it's umount!Where would you put the unmount command?
You can manually 'systemd-umount' or 'systemctl stop'.
systemd gracefully shuts down all types of mounts and I have thousands of accumulated hours with no issues. I do use --automount=yes for physical device mounts to avoid unclean dismounts. There is some testing still ongoing for that with no issues yet. Technically there is no such thing as an improper unmount of a tmpfs, it doesn't care. I will mention though that it is possible to orphan memory when an open file handle in tmpfs is deleted while a program has the file open. We can remove and recreate the tmpfs in that case, or reboot. Again, the DVR has been up for a few years now, it seems safe enough...
No, they don't.3) Many applications use .cache as a persistence directory.
I hold fast, that's a bug. @sunrat clarified it. Passwords are not in .cache, all configuration is in ~/.mozilla. Personally, it is a bug that it is not ~/.config/mozilla. I don't use thunderbird - so there's some homework for you. By 'continuity' I mean appearance, not function. Think of something like tumbler that needs to read and create all those little icons again - an annoying pause maybe but not a show stopper.if something in cache is critical to the next boots operation we should consider it a bug and file on the offending package.
Example - notice the date
https://bugs.debian.org/cgi-bin/bugrepo ... bug=747850
Again, I have years of practice of transfering (migrating) only a chosen slice of user home when a new backing is introduced and have never included ~/.cache. I suppose that is the origin of this realization to wipe it on every boot. It is doing exactly what I wanted btw, minimizing qcow2 file size creep. On bare metal it will save some wear.
Most 'dot' files are integrated into the backing layer and not backed up. This practice is a form of 'immutable' without being immutable. the layer2 qcow2 can be mangled, the backing cannot. The equivelant on a bare metal system is similar, only a small slice of home is backed up and injected when a new image is written to the disk. I 'forwardup' instead of backup the OS. All systems have an up to date vm ready to take over a running system, after the short time it takes to image to disk. All xdg directories (Documents, Music, Videos, etc) are separately maintained and often a profile mount. Mostly a future thing for bare metal once virtfs block drivers are matured - which is now and I'm late...
An example teaser - disk_ext4_music_0000_run.qcow2 to be served up and mounted in ~/Music by ~/.profile.
Backed up offline as disk_ext4_music_2403_archive.qcow2, no change since week 3 of 2024. I have yet to find a flaw in storing large qcow2's as a backup method. And yes there is more than one copy.
Someday. I mention this tangent info since it is ~/profile systemd-mount that ties it all together. Despite the complexity of the back end, the user foreground config is very simplified.
Yes, I should mention. I'm always talking about Xfce, and only Xfce. I do ask for and appreciate when others test my wild ideas under alternative desktops, but I do not do so myself. Also I'm biased towards desktops and up with ample memory. I'll also invite anyone to test smb, nfs, or other uses for ~/.profile. I think I've hinted at the request a few times, nobody has taken the challenge. I no longer use them preferring temporary jit access (just in time).Just for my reference, what Desktop environment are you using on your Debian? And are you on Debian 12.7 with Kernel release 6.1.0-25?
History;
Actually this goes back to Stretch, all kernel and Debian versions since. Elements of implementation have matured continuously and I've backtracked to earlier versions mostly for curiosity, but also to demonstrate (to me) how slow we change habits - and how long this functionality has been baked in. On these forums I think I have mentioned tidbits about polkit use for example, which is important here, that were not included until Buster or Bullseye and still absent for some DE's. Some examples are the policy files that declare an action need to be included with the appropriate package. Or missing agents when password entry is desired. For example, /usr/share/polkit-1/actions/org.xfce.xfce4-terminal.policy is still not included. That is from 2018 and in all my images since Stretch. One reason is fear, beginners do stupid things. A better reason is 'conflation factors' that we don't find immediately, or near term, or sometimes for years. So I do stupid things in vms where it's safe, mostly. I try my best to not mention certain methods until there is a history of known good without complications. The mentioned unmount is an example that was not present until later, requiring 'systemctl stop' instead of systemd-umount. Hard to believe the missing 'n' was preserved... Details run deep!
Statistics: Posted by CwF — 2024-09-06 18:08