So I'd like to split my passwords file into multiple "files", where the unimportant logins are permanently unlocked for convenience, while the more sensitive login credentials remain encrypted until I actually need them.
And how should that protect you against an attack that has compromised your system? If the system is compromised, then an additional lock does not hinder the attacker to wait until you open it.
The tweet he commented on was indeed a nice idea, but a CEO should have more foresight that the things Trump stated in it would not be true.
When you look at it now, it looks like it was more or less a threat that led to a closer relationship between "tech bros" and the current administration instead of the "take down" of them.
Immich requires to be run on a server to function, but a lot of (or even all) of its functions are things that could reasonably done entirely on-device. Aves combined with some automatic backup solution such as Nextcloud gets (from what I can tell) most of the functionality Immich offers.
How would you backup Immich on device?
And if you backup to Nextcloud than you already have a served?
So you are arguing that having a file server is enough?
And processing is done on client side?
That would be in this case very inefficient.
You would need to have all the data on the Client or transfer all the data to the client once you load it.
You device has to do all the processing which would lead to lower battery life.
How do you handle multiple Users? Giving partially access to the Filesystem?
I could come up with other points but this should give you an idea. Yes, for some use cases a server-client approach does not make sense but for a dedicated photo backup and indexer it absolutely does.
I am fully backing up my Mail Server with some exclusions like /tmp etc. with restic now for over a year, including updated binaries and docker images etc. and have about 16GB of data with hourly backups for over a year.
If you use any kind of deduplication and or compression, the system files do not amount to any meaningful size (assuming there is no additional encryption on the VM disks). Especially when you consider the size of OPs data, 1,5TB, then the couple of GB of system binaries etc. do not really matter.
Depends on the root setting. And depends on your goal. What is the purpose of the proxy? I doubt that it is easy to bypass, but you still could run a Proxy or VPN as user, this would not bypass the proxy but any filtering/blocking would not be possible. Etc
I'm also of the opinion that if a bad actor capable of navigating the linux file system and getting my information from it has physical access to my disk, it's game over anyway.
I am sorry but that is BS. Encryption is not easy to break like in some Movies.
If you are referring to that a bad actor breaks in and modifies your hardware with for example a keylogger/sniffer or something then that is something disk encryption does not really defend against.
That's also my take on the topic and that is also what backblazes data is suggesting. Would they not believe it themself then they would stop buying unreliable drives. Every brand can have outlier models that have a bad failure rate.
Go with the drive with the best money/TB rate that meets your criterias. I would consider everything above ironwolf or red plus fitting for NAS use.
Data center drives are in my experience often cheaper than NAS drives. (wd ultrastar or seagate exos or toshiba enterprise capacity)
Look for the warranty. Some times another drive for just a couple of bucks gives you a way longer warranty.
And as backblaze says themselves every time, this data is not.the complete truth either, they have large sample size but this sample size is still too small to large claims about reliability. Especially about brand reliability.
In Linux systems, initrd (initial ramdisk) is a scheme for loading a temporary root file system into memory, to be used as part of the Linux startup process. initrd and initramfs (from INITial RAM File System) refer to two different methods of achieving this. Both are commonly used to make preparations before the real root file system can be mounted.
As i said 2 different things, initrd was used to create a ramdisk, a block device. Initramfs basically directly offers a filesystem instead of a block device.
How are those devices affected by having no notification anymore? The manual labor exists anyway.
Most network switches and devices have a web gui to switch them out. Those can be automated.