I bought an $800 half stack guitar amplifier in 2009 and rarely play with the volume above 1, let alone play shows with it. But it looks neat.
When a campaign hires staffers like Stephen Miller, and the candidate has said neo-nazis and white supremacists are fine people, that right there is likely the reason.
I wouldn’t want to sleep in the same zipcode as that choad.
When I stare and blink my eyes I see Joe Pesci, maybe from how I was raised.
deleted by creator
Correct, it’s not obvious when first diving in but the main use for RAID is increasing performance and availability by allowing up to a specific number of drive failures. For that to work, ideally in an enterprise you’d have a primary and secondary controller to mitigate that point of failure which is not typical for most homelabs and makes backup even more important.
After using some grandfathered T-Mobile family plan for over a decade I moved us to Tello. Still the same towers, but with our usage it’s half the price.
One note which may not apply to you, I installed my Proxmox to boot from 2 256G SSDs as a basic RAID 1 mirror and only have the bare minimum data in VM storage to reduce size of backups. Backup retention on the boot drives is limited because a cron job on the VM handles copying backups to the MergerFS pool for longer term storage.
Moving docker’s data directory to the ‘slow’ drives was a helpful decision, this post covers the old/wrong ways to do that and the way which worked (data-root). Docker data doesn’t take up a huge amount of space, but it saved me some work recently when I found my media server had been down for a while and couldn’t remember when it worked last to identify a working backup. I spun up a fresh Debian image and ran through the steps to reinstall the stack, and point to the same Docker data path. Running the same Docker compose command got most services working with the old metadata, though others i renamed/removed the service’s path and reconfigured.
My docker-compose and its revisions are the extent of a backup I need for a piracy box as my internet is quick enough to recreate my library within a couple days if needed.
Tried OpenMediaVault but found vanilla Debian on Proxmox is the easiest to troubleshoot. This guide helped me set it up. MergerFS works great with mismatched sizes of drives, and doing parity on media server content is a good use for SnapRAID.
Put a sepia filter on it if you want to get creative.…orhideadickbutt
deleted by creator
deleted by creator
In OP’s case it sounds like the VPN service is the whole reason they’re using it. Not that I would recommend it, as their corporate IT likely has a policy against exactly this sort of thing
deleted by creator
deleted by creator
If u are being force fed corn against your will respond with a 🌽 emoji
Really liked how you worded that. It reminded me of this video about afterlife I rewatch when I’m having an existential crisis. One quote from the video,
“Ironically enough the only part of me that is immortal, for all intents and purposes, is my material body. Because after I die, and after our Sun dies, and after the planetary nebula it leaves behind fades away, every atom of me will be recycled back into the universe. Ultimately becoming part of other planets and stars. We are originally star dust literally, and we will be star dust again.”
We all do better when we all do better.
As someone who has only worked freight in an air-conditioned warehouse, moving boxes is not easy work and not many people will be able to do it their whole careers. I’m personally glad I argue with computers for my job now and I have much respect for those lifting things in the elements.
If you don’t need realtime parity, I’ve had no issues on my media server running mismatched drives pooled via MergerFS with SnapRAID doing scheduled parity.