Then Linus responded pretty poorly (and ended up stepping down as CEO and is now a chief creative something or other iirc)
Linus didn’t step down in response to this. I don’t remember the exact timelines, but he either stepped down before this, or was in already in the process of transitioning to the new CEO when this happened.
To native English speakers, yes. To non-native speakers, this is yet another bizarre rule they just have to memorize.
This is great to hear! The lack of Android Auto support was pretty much the only thing stopping me from considering a Pixel+GrapheneOS. My Galaxy S10 still has some life left in it, but I’ll probably consider replacing it with the Pixel 9 or 8a whenever those come out next year.
The more bits per cell you store, the more dense and therefore cheaper your flash chips can be for a give capacity. The downside is that it is slower and less reliable since you have to be able to write and read exponentially more voltage states per cell, e.g. 2 states for SLC, 4 states for MLC, 8 states for TLC, etc.
The Trine series is pretty fun. It’s a 2.5d puzzle platformer game. There are some combat bits, but most of the game is puzzles. I’d recommend the second one.
He killed four of his classmates and wounded seven others. 15 years old is old enough to know how terrible the impact of his actions would be. There is certainly more that we as a society could have done to help him with his mental illness, but that does not erase his agency and make him not responsible for his crimes. He has more than earned his punishment.
the timer has no idea if it was triggered during last boot. It only has the context of “this” boot, so it will do it right after a reboot and set a timer to start the service again after a week of uptime.
This is not correct. Persistent=true saves the last time the timer was run on disk. From the systemd.timer man page:
Takes a boolean argument. If true, the time when the service unit was last triggered is stored on disk. When the timer is activated, the service unit is triggered immediately if it would have been triggered at least once during the time when the timer was inactive.
OP needs to remove Requires=backup.service from the [] section so it stops running it when it start the timer on boot.
You have the timer requiring backup.service, so it will run that service every time the timer starts on boot. Remove Requires=backup.service, and that will fix the issue.
Well, for one, it’s network attached storage. If it’s not present in the network for one reason or another, guess what, your OS doesn’t boot… or it errors during boot, depending on how the kernel was compiled and what switches your bootloader sends to the kernel during boot.
Just use nofail in the fstab.
Second, this is an easy way for malware to spread, especially if it’s set to run after user logon.
If your fileshare is accessible to you, it is also accessible to malware running as your user. Mounting the share via a filemanager doesn’t change this.
I’ve been using PhotoPrism for the past couple of days and have really liked it.
I was considering Immich, but the rapid development cycle turned me off of it for now. I don’t want to have to deal with keeping up with patch notes and potential breaking changes. Immich also seems more focused on photo backups from your phone, which isn’t quite what I wanted. PhotoPrism just let me upload all my existing photos on the web ui.
I’d say give both a try. Both provide a docker-compose file, so you should be able to bring them up fairly quick.
I think the snapshot exists but is not mounted as a btrfs subvolume.
Is it not listed when you try running btrfs subvolume list .? You might need to change the . to a path that is on the array.
from the research I did, the @docker folder at the volume root holds all the volumes, images, subvolumes, etc. and I did copy that over.
Copying over the files wouldn’t be enough. You would actually need to create the subvolumes, e.g. btrfs subvolume create subvolume_name.
Do you happen to know if I find the snapshot folder and download it, will there be anything recoverable? Or would it just be like, hashes and unintelligble stuff?
Unfortunately, I am not familiar enough with how Synology does things, but a btrfs snapshot will just appear as normal directory with the files/directories in it. If Synology isn’t using btrfs for the snapshoting, I’m not sure what you’ll find.
I’ll preface this by saying I am not familiar with Synology, but I am using Docker and BTRFS (which I am assuming is being used on your Synology NAS).
Do you have SSH access or the ability to get a shell on the NAS? If you do, you can try running btrfs subvolume list . to see what subvolumes/snapshots are on your system. That will hopefully let you figure out where your data is. Once you narrow down where it is, you can try downloading it using an sftp client.
As an aside, the reason Docker threw a fit whenever you tried to update an image is that Docker was probably automatically using the BTRFS driver, which creates a new subvolume/snapshot for every image/layer. When you remove images, it would just remove all the subvolumes/snapshots. When you copied your files over, you probably didn’t remake the subvolumes. That would have caused issues when trying to remove images, or create new images/containers.
How are you passing the drives to the TrueNAS VM?
It’s your private key, but yes, you would need to keep it secret just like you would an SSH key.
The benefits of a VPN are that you don’t need to open ports up to the internet and rely on your individual services to be secure. Your VPN would authenticate users and ensure that the communication over the tunnel is encrypted (useful if you don’t want to set up SSL/https). They can also hide what services you are hosting or even hide the fact that you are even running a VPN.
Private keys are going to be far more secure than passwords since you really can’t brute force them in the same way you can passwords. Getting ahold of someone’s private key is probably going to be far more difficult than guessing their password. Even if an attacker were to get ahold of your private key, they would still need to contend with the security of your service, e.g. logging into it, which would be no worse than not having a VPN.
Texas does have anti-SLAPP laws passed and they are among the strongest in the nation. Unfortunately, the courts have ruled that they cannot be used in federal courts.