Was asked quite a few times how I do my backups with Restic.
For more than 10 years I was using “Duplicity” for backups, but in 2019 I changed to Restic. The main reason for the change was that Duplicity still can’t handle “Big Data”, as in: larger directories. In 2009 someone opened an issue on the Duplicity bugtracker, and this problem still exists as of today. For about two years I was shifting around the problem, excluding files, trying to make the sigfile smaller. But at some point I decided that it is enough and I need to change the tool.
Installed my new laptop, and everything seemed to work, out of the box. Almost everything.
The audio was quite annoying. First of all, every application got it’s own volume setting. In theory that is a nice idea, and you can control and manage the volume for every application separately. In practice, this is a nightmare: try changing the volume of an application which only once in a while sends a short notification. Or try changing the volume of the sound when you close the laptop lid. On top of that, the volume for applications like Chome and Firefox seem to be stuck at 100%. Every time I change the volume, the setting is back on “loud” the next time the browser plays something.
When I go Scuba Diving, I use two diving computers. It’s always good to have a fallback, right? My main computer is a ScubaPro Uwatec Galileo Luna. That’s a wrist mounted computer with hoseless air-integration. That means that a sender is connected to the first stage of the regulator, and it transmits data to the wrist computer. In addition the computer records data like depths, consumption, temperature, alarms ect. My fallback is an air-integrated console mounted Suuntu Cobra. I check this computer too when I’m under water, but mostly for the most conservative reading for the safety stop.
If a disk failure happens, the disk is replaced with a similar disk, and then needs to be configured and re-added to the RAID.
Everybody likes systemd, right? Well, not everybody. Who thought it might be a good idea to replace existing init systems with something which is big, monolithic, and not even feature complete?
A simple task: execute a script when an interface comes up, or goes down.
In the old days, on Debian or Ubuntu, one just added
post-down scripts in
/etc/network/interfaces. But now, that file is gone, or empty. Ubuntu comes with
netplan, which nobody else seems to use - luckily. NetworkManager is not used all the time, so one can’t depend on that either. And systemd does not have an option to do something simple like taking care of interfaces coming up and down. You can write yourself a target, but that only fires for the first time, not every time.