I have bought a few otherwise hard to find books on Amazon. Actual paper books. At least used to be possible.
- 0 Posts
- 10 Comments
TXL@sopuli.xyzto Selfhosted@lemmy.world•Handbrake local vs docker on Synology DS920+: same settings, very different results?English7·27 days agoIf all the settings and versions match, my first suspicion would be that there’s some library available on one system that gets used but not the other. Have you taken very verbose logs to see if there’s differences that stand out?
https://www.debian.org/ports/m68k/ has a nice little intro and the key requirements.
MMU and HD space were the biggest issues. One of those has pretty much gone away with time.
Beware that you won’t have ECC, so corruption is much more likely than with proper hardware.
TXL@sopuli.xyzto Linux@lemmy.ml•Zorin OS 17.3 replaced the default Browser from Firefox(Old) to Brave(New).1·5 months agoBrave is a series scam company. There are only two reasons anyone would support them: They were scammed, or they joined in the scam.
TXL@sopuli.xyzto Linux@lemmy.ml•Zorin OS 17.3 replaced the default Browser from Firefox(Old) to Brave(New).0·5 months agoHow’s the ad blocking or add-ons? Last I looked there was none.
Nothing has beat mutt so far. But that’s not for everyone, naturally.
TXL@sopuli.xyzto Linux@lemmy.ml•Those who use DWM, how do you get the autostart scripts to work?0·5 months agoIt’s not a file name. It’s shell syntax. Specifically, https://en.wikipedia.org/wiki/Job_control_(Unix)
That’s a pretty terrible article on the subject, but I don’t have a better one at hand. You could read some shell scripting tutorial or manual or maybe a beginners guide to Unix. A decent one should explain job control well.
But basically, in a script or command line, an ampersand ends a command and runs it in the background without waiting for it to finish before running the next command. A semicolon works the same but waits on the foreground.
In my experience it’s also very very hard to wear out an SSD. It’s limited, but mostly the limit is very very far away. I treat those warnings as largely fud. Most common failure more seems to be that the controller in the drive dies for some reason and the drive just goes completely dead and never gets detected again. There won’t be warnings from any smart values either.
Or the drive is just replaced with a bigger faster one, maybe on a different bus/connector or something, and forgotten in a drawer or a box somewhere.
Naturally it’s still worth trying to enable trim and limit writes if there’s no downside. It can only help in case the drive does get an exceptionally long service life. But I’d say use it while it’s still useful and keep fresh and verified backups.