this post was submitted on 02 Oct 2025
343 points (93.4% liked)
Technology
75707 readers
5360 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Just today at work other team wrote a bunch of ready-made images on their SBCs. In about 10% of them snap shat the bed by corrupting one json file which rendered their environment unusable. They did it in a pretty stupid way by writing an sd card, inserting it into SBC, booting up and disconnecting power after very short visual confirmation that system gave some signs of life. And snap was doing whatever it's doing in the background. So I had the pleasure of removing said json-file and reinstalling all their crap manually on those failed units.
So, maybe not strictly speaking fault of snapd, but yet another problem it caused for me without any practical reason other than the environment they chose just uses snap instead of something more robust.
Raspberry pi's didn't even have power buttons until this latest version. I fully expect to be able to unplug an SBC at any point with very low chances of corruption. It's not like they're designed for that, but they don't really give you much choice. Having 10% fail like that is ridiculous.
In fact, I've done it hundreds of times and never had an issue.