Same thing happened a couple years ago.

What about governments?

and win11 has it too.

Why on earth did they decide to call thread creation "forking", when process creation has been called "forking" for 50 years? Is it to cause deliberate confusion, or was it designed by someone who's never heard of unix?

What if I told you shareholders also live in communities? And that those profiles are providing retirees with income. Also, governments start wars, not companies. Governments are not altruistic as a whole, and it's generally the exception when they are. Charities can be, as a whole.

Are parties illegal in NYC? What are they monitoring for? Even the article doesn't say. Bizarre.

Doesn't x86 have address-space #s now? (Like other arches have had for decades.) If the working set for the TLB is close to its total size, then it wouldn't help much, but if it's a problem of TLB-invalidate on context switch, address space numbers allow the TLB and other virtually addressed caches to avoid flushing entries that might hit again when context is switched back.

It's shame they never offered any 4k blurays.

Looks like they're still pretending blurays are a type of dvd.

It's bizarre the article makes no mention of blurays. DVD quality is horrible and nearly unwatchable, except for old 480i TV shows. Netflix also bizarrely refers to all discs as "DVD", even in the domain (dvd.netflix.com).

I still rent blurays occasionally from netflix. It's a real shame they still have not added 4k blurays, which are superior both in video and audio to any streaming that's available. I've resorted to buying and reselling 4k blurays on ebay as a workaround for renting.

This story is a repost.

Checksumming means you're defeating zero-copy sendfile() by having the cpu read from ram. It will lower perf.

Didn't even read the summary. He used a laptop instead.

LG phones were better. Headphone jacks, and removable batteries until the g6.

I wrote a file and device wiper, but these days I just set whole-device encryption with an ephemeral key and dd /dev/zero to the encrypted device. It's just as fast, but a little more secure. It's always best to encrypt data in the first place, but there is still risk of a leak, if the keys are leaked as well, so still best to overwrite at least the area were intermediate keys are stored (like freebsd's geli does, to allow master key changes).

Whether or not slightly misaligned overwrites might allow for recovery (especially if a fixed pattern like all 0s is overwritten), or if subtraction of the pattern is possible at all, I don't know. The most-paranoid might still have an argument for destruction. No one taking that prize doesn't mean a nation-state doesn't have the capability. There might be test equipment with enough resolution/sensitivity. It makes sense that mass produced heads and servos are not the most precise.