overview for traches

colors rule by traches in c/196@lemmy.blahaj.zone

[-] traches@sh.itjust.works 9 points 15 hours ago

That’s not really true, we can definitely see yellow light. Red receptors and green receptors are both sensitive to it, which your brain correctly interprets as yellow.

I hate the day and like the night: I accidentally typed out too much into a comment about night shift vs day shift, so it's a 196 post now ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯ (to follow the rule) by traches in c/196@lemmy.blahaj.zone

[-] traches@sh.itjust.works 12 points 3 days ago

I love your writing OP

There are daytime people and nighttime people and they marry each other

Quite an explosive finish by traches in c/noncredibledefense@sh.itjust.works

[-] traches@sh.itjust.works 21 points 5 days ago

Baby unit tests by traches in c/programming@programming.dev

[-] traches@sh.itjust.works 8 points 6 days ago

I mean I agree but you don’t have to be a dick about it

Baby unit tests by traches in c/programming@programming.dev

[-] traches@sh.itjust.works 40 points 6 days ago

I don’t get the hatred for types, they have saved my ass so many times and saved so many headaches exactly like what the article describes. I used to write a lot of ruby and after getting decent at typescript I can’t go back.

It’s not just ceremony, types ensure some level of logical consistency in your app. They reduce how much of the world you need to keep in your head at one time, and they allow you to express your intent far more robustly than comments and naming can. I love rust’s approach of making invalid state not even representable.

Abstractons by traches in c/programmerhumor@lemmy.ml

[-] traches@sh.itjust.works 5 points 6 days ago

Yeah, docker in a VM makes sense. Docker in docker in a vm in a vm though?

What were you wrong about for a long time? How did you realize you were wrong? by traches in c/asklemmy@lemmy.world

[-] traches@sh.itjust.works 115 points 1 month ago

Raised conservative christian, took a disgustingly long time to lose some of my shittier takes

Legitimately ugly rule by traches in c/196@lemmy.blahaj.zone

[-] traches@sh.itjust.works 172 points 3 months ago

They didn’t even clean up the rubble

46

Best way to keep a hot spare SD card for a raspberry pi? (sh.itjust.works)

submitted 3 months ago by traches@sh.itjust.works to c/selfhosted@lemmy.world

54 comments fedilink

I have a load-bearing raspberry pi on my network - it runs a DNS server, zigbee2mqtt, unifi controller, and a restic rest server. This raspberry pi, as is tradition, boots from a microSD card. As we all know, microSD cards suck a little bit and die pretty often; I've personally had this happen not all that long ago.

I'd like to keep a reasonably up-to-date hot spare ready, so when it does give up the ghost I can just swap them out and move on with my life. I can think of a few ways to accomplish this, but I'm not really sure what's the best:

The simplest is probably cron + dd, but I'm worried about filesystem corruption from imaging a running system and could this also wear out the spare card?
recreate partition structure, create an fstab with new UUIDs, rsync everything else. Backups are incremental and we won't get filesystem corruption, but we still aren't taking a point-in-time backup which means data files could be inconsistent with each other. (honestly unlikely with the services I'm running.)
Migrate to BTRFS or ZFS, send/receive snapshots. This would be annoying to set up because I'd need to switch the rpi's filesystem, but once done I think this might be the best option? We get incremental updates, point-in-time backups, and even rollback on the original card if I want it.

I'm thinking out loud a little bit here, but do y'all have any thoughts? I think I'm leaning towards ZFS or BTRFS.

Pornhub Pulls Out of Nebraska by traches in c/news@lemmy.world