

But what if they don’t fully own the shell company that owns the houses, do they need a majority stake?
I joined Lemmy back in 2020 and have been using it as qaz@lemmy.ml until somewhere in 2023 when I switched to lemmy.world. I’m interested in systemd/Linux, FOSS, and Selfhosting.
But what if they don’t fully own the shell company that owns the houses, do they need a majority stake?
I checked and while it seems to certainly have an influence, it doesn’t seem to be the main thing making a difference.
Isn’t eye strain mostly due to distance?
This is the game that is built on SpacetimeDB. It’s quite an interesting project.
I’m talking about the implementation of RAID5/6 for BTRFS specifically.
The RAID56 feature provides striping and parity over several devices, same as the traditional RAID5/6. There are some implementation and design deficiencies that make it unreliable for some corner cases and the feature should not be used in production, only for evaluation or testing. The power failure safety for metadata with RAID56 is not 100%.
Do you know if the documentation is outdated? Has this changed recently?
It used to eat data but that’s not been the case for a few years
Isn’t that a RAID5/6 thing?
I’ve always imagined it being the Venn diagram intersection of high IQ and arrogance, is that correct?
Maybe so you can hire people from overseas?
Yes, but you shouldn’t be using Chrome anyway 🤷
You might not have noticed but 90% of these posts come from the same user
?
I recommend using systemd services and/or docker compose instead. systemd services are files that describe which program / script to run and when (like after networking is active or after a certain other service is loaded).
I use OpenSUSE Tumbleweed because it focuses more on KDE than GNOME, is quite stable, and has snapshots to roll back to in case something does go wrong. I don’t want to mess with my OS, I just want it to work reliably. I do use Debian on some devices (like my server) but the software (especially in terms of GUI apps) is very outdated and it doesn’t come with the other features of OpenSUSE out of the box.
At least 1
Uhh, with DST?
Just always use the good format
Security, a malicious individual could mitm or impersonate another server when the private key is leaked. Reducing the timespan from the current 398 days reduces the amount of time compromised certificates can be used. It is possible to revoke certificates, but I think this is for cases when devices are unable to receive those messages.
They missed out on calling it macrodots
I haven’t seen any extreme comments coming from infosec either.