Powercycling is not healthy lol
Powercycling is not healthy lol
To me, the appeal is that my workflow depends less on my computer and more on my ability to connect to a server that handles everything for me. Workstation, laptop or phone? Doesn’t matter, just connect to the right IPs and get working. Linux is, of course, the holy grail of interoperability, and I’m all Linux. With a little bit of set up, I can make a lot of things talk to each other seamlessly. SMB on Windows is a nightmare but on Linux if I set up SSH keys then I can just open a file manager and type sftp://<hostname> and now I’m browsing that machine as if it was a local folder. I can do a lot of work from my genuinely-trash laptop because it’s the server that’s doing the heavy lifting
TL;DR -
My workflow becomes “client agnostic” and I value that a lot
My list in order of desperation, lowest first
I recommend it over a full disk backup because I can automate it. I can’t automate full disk backups as I can’t run dd reliably from a system that is itself already running.
It’s mostly just to ensure that I have config files and other stuff I’ve spent years building be available in the case of a total collapse so I don’t have to rebuilt from scratch. In the case of containers, those have snapshots. Anytime I’m working on one, I drop a snapshot first so I can revert if it breaks. That’s essentially a full disk backup but it’s exclusive to containers.
edit: if your goal is to minimize downtime in case of disk failure, you could just use RAID
My method requires that the drives be plugged in at all times, but it’s completely automatic.
I use rsync from a central ‘backups’ container that pulls folders from other containers and machines. These are organized in
/BACKUPS/(machine/container)_hostname/...
The /BACKUPS/
folder is then pushed to an offsite container I have sitting at a friends place across town.
For example, I backup my home folder on my desktop which looks like this on the backup container
/BACKUPS/Machine_Apollo/home/dork/
This setup is not impervious to bitflips a far as I’m aware (it has never happened). If a bit flip happens upstream, it will be pushed to backups and become irrecoverable.
The point of having the RSS reader somewhere not on my PC is that when I reinstall my PC it’s one less thing to configure again. I just open the browser bookmark and there it is exactly as I left it.
I don’t get it. You think laws will stop existing if we stop paying some fat cats for sitting on some copyrights?
I also don’t care what I’m allowed to do, I don’t believe in copyrights, so you can’t really argue in favor of it to me.
That’s semantics. They’re charging it because they’re afraid you’re copying copy-protected materials, which is piracy. It’s a piracy tax.
is not about paying for pirate copies, but it’s a compensation for the loss due to the right to a private copy.
Sounds an awful lot like a piracy tax… We pay this tax on any device which can store bits, it’s not just some storage mediums. If you buy a phone, you’re paying this tax to a “”“non-profit”“” org called CopyDan whose sole job is to make sure a few select fat cat copyright holders get paid. If I don’t break their copyright, I still have to pay as if I did. Therefore, it’s a piracy tax.
Actually it might be blankmedieafgiften, that sounds far more correct. I was having trouble finding the exact term and ChatGPT was very confident (I know…) when I eventually gave up and asked it.
I don’t have to worry about any of this because I live in Denmark! It is not possible for me to pirate stuff because it implies that I did not pay, which I did as there is a special piracy tax!
We call it ‘blankmedieafgiften’.
we call it ‘kulturarvsafgiften’ and apparently you can’t google it which I’m not gonna imply any conspiracies about but yknow
Iteration one, the original https://drkt.eu/library/Museum/old_website_hw.jpg
Iteration two, taking it seriously https://drkt.eu/library/Museum/ye_olde_server-rack.jpg
Iteration three, evolved LACK rack https://drkt.eu/library/Museum/new_apartment.jpg
Bonus https://drkt.eu/library/Museum/backside_mess.jpg
'Artemis' Server
MOBO : GigaByte MB GA-Z170XP-SLI
CPU : Intel Core i5 6600K 4c/4t
RAM : 2x DDR4 8GB CL14 2133 Kingston HyperX
PSU : ## TO BE ADDED ##
Storage - SATA : SSD 2TB
- SATA : HDD 4TB
- SATA : SSD 1TB
'Deimos' Server
MOBO : ASRock H81M-ITX
CPU : Intel Pentium G3220 2c/2t
RAM : 2x DDR3 8GB C8 1600 Crucial Ballistix OC
PSU : ## TO BE ADDED ##
Storage - SATA : HDD 300GB
'Phobos' Server
MOBO : Intel H81 Express Chipset
CPU : Intel Core i3 4330T 2c/4t
RAM : 2x DDR3 4GB 1333
PSU : 65 watts AC/DC adapter
Storage - SATA : SSD 2TB
The misunderstanding seems to be between software and hardware. It is good to reboot Windows and some other operating systems because they accumulate errors and quirks. It is not good to powercycle your hardware, though. It increases wear.
I’m not on an OS that needs to be rebooted, I count my uptime in months.
I don’t want you to pick up a new anxiety about rebooting your PC, though. Components are built to last, generally speaking. Even if you powercycled your PC 5 times daily you’d most likely upgrade your hardware long before it wears out.