ccryx [he/him]

I’ve finally pinned down my backup automaton:

• All my services are in podman containers/pods managed by systemd.
• All services are PartOf= a custom containers.target.
• All data is stored on btrfs sub volumes
• I created a systemd service that Conflicts=containers.target for creating read only snapshots of the relevant subvolumes.
• That service Wants=borgmatic.service wich creates a borg backup of the snapshots on a removable drive. It also starts containers.target on success or failure since the containers are not required to be stopped anymore.
• After borg backup is done, the repository gets rclone synced to an S3 compatible storage.
• This happens daily, though I might put the sync to S3 on a different schedule, depending how much bandwidth subsequent syncs will consume.

What I’m not super happy about is the starting of containers.target via the systemd unit’s OnSuccess= mechanism but I couldn’t find an elegant way of stopping the target while the snapshots were being created and then restarting the target through the other dependency mechanisms.

I also realize it’s a bit fragile, since subsequent backup steps are started even if previous steps fail. But in the worst case that should just lead to either no data being written (if the mount is missing) or backing up the same data twice (not a problem due to deduplication).

kmail is in the arch repository (in extra), the package is called kmail.

Scientists are this world’s wizards

Sourceforge has stopped distributing adware installers again since they changed ownership a few years ago.

g is the acceleration applied by Earth’s gravitational force (for masses much smaller than Earth’s, that are pretty close, i.e. essentially everything you typically interact with) and is approximately 9.81 m/s^2

IIRC you have to have the app installed on your phone and be in the same network, but it’s been a while.

I did use franz at some point but eventually switched to ferdium, which doesn’t require an account. That being said I haven’t used either for a while now.

• For your first point you’d probably want to investigate why your system doesn’t suspend or what exactly is going on. You could check logind.conf, specifically the HandleLidSwitch* keys. Otherwise, your lid switch should have a corresponding /dev/input/ event that you could maybe listen to or something.

• I can’t offer much input on your second point. I think unplugging the audio jack should probably trigger a udev event that you could write a rule for. No idea about wireplumber though.

Just fyi, while it’s possible to have end to end encrypted chats in telegram, they aren’t enabled by default.