MacOS is basically a different world.
The KDE team has already determined that this is not a bug and that both you and me must just be imagining it:
Floating Point Unit. The thing that does mathematical operations on floating point numbers. It used come separately from the CPU as an add-on chip, but around the 486 era, manufacturers started integrating it on the same die as the CPU. Of course, as these things go, from the system programmers point of view, there is still no difference between an add-on FPU and an integrated one.
The one pictured here is an add-on FPU for an Intel 80386 CPU.
About 20 years ago, Microsoft was found guilty and convicted, because they forced their browser on their users, driving out competitors by abusing their de facto monopoly on PC operating systems. These days, they are doing the exact same thing again, just on an even broader base. I don’t even understand how this verdict took so long.
But this is about companies, not products or brand names.
WhatsApp is not its own company, it belongs to Facebook/Meta.
Also, on that topic, you could do the same thing you did with X/Twitter to Meta/Facebook.
*edit: Oh, and of course Alphabet/Google. Curious how many big tech companies seem keen on obfuscating their own name these days…
Smartctl works on nvme drives. Use it.
btop for bling
htop for practical utility
top for minimalism, availability, reliability
Well, yeah, dividing something by 0.5 is the same thing as multiplying it by 2…
Top Left – More or less the default position, sensible enough, if a bit naive. Nothing wrong with this.
Top Right – Having knowledge is a good thing, and so is making decisions based on sound risk-benefit analysis.
Bottom Right – Well, at least it’s an informed decision. Just don’t try to pass off the risk on someone else if it backfires.
Bottom Left – Oooouuuuh, you don’t want to be in this quadrant, trust me…
Batteries take “rare earth metals” like cobalt.
Some Lithium-Ion batteries use Cobalt, but many don’t. Lithium-Iron-Phosphate, for example, is a popular variant without any Cobalt. There is a push going on to move to battery chemistries without Cobalt or to reduce the actual amount of Cobalt where it is still required.
The way I, as another European, understand this, he’s flying an anti-oppression flag and a pro-oppression flag at the same time.
Several years ago now. On at least two of those tries, after maybe a month or some of daily driving, suddenly the fs goes totally unresponsive and because it’s the entire system, could only reboot. FS is corrupted and won’t recover. There is no fsck. There is no recovery. Total data loss.
Could you narrow it down to just how long ago? BTRFS took a very long time to stabilise, so that could possibly make a difference here. Also, do you remember if you were using any special features, especially RAID, and if RAID, which level?
Out of interest, since I’ve not used the “recommended partion setup” for any install for a while now, is ext4 still the default on most distros?
I recently installed Nobara Linux on an additional drive, because after 20 years, I wanted to give Linux gaming another shot (works a lot better than I had hopes for, btw), and it defaulted to btrfs. I’ll assume so does Fedora, because I cannot imagine Nobara changed that part over the Fedora base for gaming purposes.
Well passwordless.
Same thing in this context. But sure, an encrypted partition would work.
Dunno about ideal, but it should work.
It does have quite a bit of overhead, meaning it’s not the fastest out there, but as long as it’s fast enough to serve the media you need, that shouldn’t matter.
Also, you need to either mount it manually on the command line whenever you need it or be comfortable with leaving your SSH private key in your media server unencrypted. Since you are already concerned with needing to encrypt file share access even in the local network, the latter might not be a good option to you.
The good part about it is, as long as you can ssh from your media server to your NAS, this should just work with no additional setup needed.
Interesting. Though it does seem to to require your private key to be unencrypted…
Is OpenBSD seriously still using CVS for development?