What all 32 bit stuff do you need to replace?

No.

No. You can’t. Have backups and get comfortable with your distributions bootloader reinstallation process.

Removed by mod

Debian will decide to allow ai code.

E: as it turns out, Debian has decided to allow ai code. I’d like to dedicate this comment and this edit to my haters.

A photocell is just a reverse transistor where the base is sunlight hitting the p instead of a small current.

Deserialization error.

It’s fine. I’ve used Debian on that machine. You’ll need to do Broadcom but that’s incredibly easy and if you find it to be too complex or hard, and I mean this as helpful assistance as opposed to an insult, it’s likely Linux isn’t really for you right now.

69

But at what cost?

Ty! I also have one of the same model, same specs, completely busted top cover that wiggles and wobbles around if they want to slum it and save some more bucks.

Tbh you should just get a mac.

You can have privacy on them with a little less effort than on windows and they’re already decently secure. They can play cyberpunk and you already have the linux (bsd) toolkit. They’re already the kind of computer you like with the good trackpad etc.

I would drop your “be European” requirement.

I can sell you a 15” dell with a quad core and 32gb of ram.

E: this is not a joke, I have a 3520 from a couple of years ago with an 11th gen i7, a 256gb nvme, the sata kit included and 32gb of ddr4. HMU.

I think they have an average 40% adoption rate?

That flattens individuals and second string kill pens into the same group though.

No one with any political power wants actual culls though and the feral mustang herd plays an important role in keeping the blm grazelands in shape for ranchers to run cows on em.

So even if you can climb the ideology mountain there’s real material forces at work preserving the feral mustang herd.

Yeah whenever blm does a roundup they shuffle the animals off to privately run kill pens that warehouse them in substandard conditions and market them to horse girls on social media.

It’s illegal to kill horses for meat in America so you gotta put em on a train to Canada where they mostly become dogfood.

But Americans don’t want them to be killed directly and instead ship the carcasses, so they hold the horses so someone can “adopt” them.

I don’t know why I used quotes there, it’s animal adoption just like a dog or cat except for the wild differences.

While the animals are held in government subsidized private kill pens they are subject to conditions that pretty much every horse owner hates.

Of course the solution is much bigger roundups with direct kills but the horse people hate that idea.

You’re barking up the wrong tree and fucking up your life by doing this.

Split the streaming/gaming duty to a different device that can be operated in the way the user expects.

Wherever you disconnect shutdown signals from will be relied upon by something down the road and you’ll end up with a weird messed up broken update when that happens.

You’ll just have to launder your purchases of Chinese parts through mouser or digikey like the big boys do.

E: try to be diligent when using farnell. They end up with weird shit sometimes.

Yes of course this will only rewrite some number of blocks that total the disks reported capacity. In the case that a person is worried about hidden blocks being preserved by a wear leveling algorithm they could just run the same command again and that would get em all.

That’s only true for some environments.

E: this is the first time I’ve read that blog post since it was published (or at least a long time ago) and there’s now a comment specifically referencing the actual behavior I observed in the wild when I tried to sub other things in for “normal” uses of dd:

Nobody says: 2016-12-30 at 15:17

cat /dev/cdrom > myfile.iso

Works

cat myfile.iso > /dev/cdrom

Won’t – dd allows you do handle writes in various block sizes, so if a device can’t handle a one-byte write, cat could well end up writing your byte followed by zeros (and because of where the pointer now is, do it again for the next byte).

Still, all your other points stand – nice piece.

While that comment was written seventy years ago, in this age of people with questionable intent, capability and integrity rewriting system tools in rust there’s no better time to linger thoughtfully over cp or cat or any number of other commands that begin with the letter “c” before grabbing the ol’ reliable footgun whose fifty years of script backwards compatibility ensure that no one can get their dd replacement accepted in normal use until it behaves as expected.

Secure erase just drops the ssd controllers table of where logical blocks are in the physical memory and trims the disk. Which is good and you should do.

That means a person would have to address the memory directly with flying leads or a bed of nails or something. Or have special software that makes the controller tell them what’s on each physical block and then put that data together into a bunch of files.

If that worries you, do dd if=/dev/urandom of=/dev/<disk> before you secure erase.

Then everything on the drive will be random static before the secure erase drops the block table and trims, so even if someone uses magic power to read the block contents directly they just get to see static.

That has the benefit of speeding up the drive by resetting read fatigue at the expense of one layer of writes which is always worth it.