Whatever’s around. Some writable filesystem.

Rsync and cron

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.

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.

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.

This is happening because you touch yourself. It’s punishment from god for the sin of onanism.

E: actually probably everyone itt is forgetting about ssd read fatigue. Rewrite every block on your ssd and the problem will go away.

Debian: the worst Linux distribution, except for all the other ones.

Long time Debian user and governance appreciator. Welcome. If you want some schizophrenia inducing reading material you should go back and check the long and well documented history of Debian voting.

First time?

You do not need to keep replying to me with insults and vitriol. I’m not trying to fight you.

I’m trying to make sure that anyone who reads your comments understands that audiobooks are not in any way a substitute for reading. I want you and anyone who also listens to podcasts or audiobooks or even those long yts to understand that they are different things.

I think that’s an important thing to do because one of the biggest differences is the type of thought each one requires and reading the written word is associated with better cognitive outcomes as a person ages.

I want you to live a long healthy life so I’m still replying :)

Listening to audiobooks engages a different way of thinking than reading the written word does. Listening to audiobooks is not reading.

That isn’t to say it’s not fun or interesting or a way to occupy your mind but it’s not the same as reading.

Please read. Listening to podcasts and audiobooks is no substitute. When you listen you’re thinking in a different way than when you’re reading and it’s important not to lose those cognitive capacities.

If you could read youd be very upset by my reply.

E: it’s really cruel to just make a funny one liner response to you. Reading and listening are two wildly different types of cognition. There is no argument against that and I don’t intend to engage with anything you present claiming otherwise. If you want to win an internet argument by having the last word about it, here’s your chance.

For your own sake please incorporate reading, actual looking at the written word and translating it into ideas, into your life especially if you’ve moved away from doing so. The process of reading has been linked in many studies with improved cognition as you age. For your own sake and the sake of the people around you, read. Do not fool yourself into believing that listening or watching is the same as reading. It will only hurt you and people who go by your example.

From Portuguese to English.

You could look at the screen, but there’s also braille terminal support.

Some people do tts but that’s questionable, even if you don’t recognize that audiobooks aren’t reading, why burn power doing tts when you could just dl the mp3s instead and make it easier on yourself.

Use ffmpeg to fix your files first so you have fewer problems.