💾 Archived View for station.martinrue.com › kevinsan › d2a2c459be1d4843a1ae42d836e373ea captured on 2024-07-09 at 01:27:37. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-01-29)
-=-=-=-=-=-=-
systemd borked my raspberry pi because a removable volume had been, um, removed. that is not a good thing. maybe systemd is not a good thing after all.
3 years ago
@mc it had an automounted entry in fstab which didn't exist on reboot. @mcoffin thanks for the tip! I agree, systemd has a lot to offer, but also a lot to hide. It's hard to figure out systemd without the docs whereas, e.g. init scripts could be easily discerned. · 3 years ago
I did that once, but it wasn't a removable drive. Turns out that setting `RequiredBy=default.target` is a really bad plan for things that really aren't that necessary. `WantedBy` will allow things to still get reached, but it will attempt to "start" those mounts. I use that now and it's been much nicer. systemd definitely has it's issues, and I don't like the "all-inclusive" philosophy, but I'll be damned if I don't miss it when I'm on my non-systemd systems. In particular, the thing I miss the most is the log file management by journalctl. If I had a dime every time I filled a disk forgetting to rotate logs on a non-systemd system, I'd be up there with Jeff Bezos · 3 years ago
systemd is evil and it has a better memory than a jelous wife. Did you unmount the removable volume before... remove it? · 3 years ago