341
Upstream images vs bazzite: https://github.com/ublue-os/countme/blob/main/growth_upstream_with_bazzite.svg
My prediction: bazzite may have more installs than Fedora KDE by the end of the year.
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Jul 2026
341 points (99.1% liked)
Linux
66531 readers
501 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 7 years ago
MODERATORS
I honestly think the kid example is a counter example. Kids now don't understand technology, because we try to keep them so far away from how it actually works. I'm very technologically literate because I was messing around with my system as a kid.
It's the same as how older generations can take apart an engine, and most people now can't even change their own oil. We try to "protect" users from the technology, and they never learn how it works. No, they should be given access to break it. That's how you learn how it functions.
Because when I finish my 10 hour shift, get home from my 2 hour commute, to my 6 year old kid crying because she managed to fuck her Minecraft machine up somehow, I don't want to spend my only free half hour that day trying to work or what she did.
That's not a learning opportunity for her. Even if she had the patience to sit there and watch me try to fix it, she won't r get what I'm doing. And after getting up at 5.30, getting home at 7.30 watch how good I am at not just swearing at the thing instead.
Rsync changes each week to a network share with an A/B layout, switching backup targets back and forth each time. Something breaks? Remote in, rsync back, by the time you get home from work it’ll be back as it was and running already.
What if you have a system that just works and you can't break?
No rsync, no remoting from work (vpn or other software et al), no "i gotta be on alert for when my kid breaks my computer again"
Also, why do we have to shame people for just wanting to use their computer?
I’m not shaming. I’m offering a simple Solution. The backups can be automated and you can NetBoot the restore process off that rsync target so you don’t have to be distracted at work. You can have a simple plan to execute if you get these calls while you are at work so there is no problem you can’t instantly reverse. It takes no time to pull off after you’ve set it up.
Think about it like this: they just want a PB&J because it's quick, simple, and works for them and you're telling them to go out to the store and get ingredients to make a salad because it's quick, simple, and works for you.
You're both right. You can eat your salad and they can eat their PB&J and all will be well in Linuxland. That's the beauty of it.
I appreciate what you are saying but there a misunderstanding. I trying to tell someone to do something.
I’m telling them a way to do something.
There’s no requirement to do things my way or even do them at all. I was trying to suggest there is an option available that might meet his criteria.
I do not agree about this being a simple solution, especially if you want to set up netboot for this, but I don't want to engage this discussion any further since we're just talking about a solution to a problem that I don't have and I don't care to solve, so maybe we should just agree to disagree?
That's a wholly different problem right there. Namely the shitty wages and unaffordable housing. With proper wages, you would have the time for your kid since it would then be sufficient that only one of the parent works full time whereas the other takes care of the kid and the house and stuff like that.
Yeah, the problem might be that you're doing it. For me, it would have been on me to fix it.
You think I should tell a You think I should tell a 6 year old kid to fix a broken Linux system? I'm sorry this has turned from discussion into bullshit.
The problem of the convo is that the other commenter talked without knowing the kid age, i agree that it's unrealistic to make a 6 years old kid fix any system at all, thought i can see a 11 years old learning that
You're underestimating children. When I was around that age I had to fix my broken PC because nobody around me knew how to (parents didn't care for Computers) and the next repair shop was far away.
My only support was some of the IT staff from School and books. I was setting up Windows 95 and making my own DOS boot floppies before I hit my teens, and I'm just the average working class person.
6yo? Maybe not, although they probably could. My point was they will learn if they have to. 6yos are capable of far more than people give them credit for. They just need an incentive. They probably won't understand the system, but they can probably fix simple issues, which is also probably the only issues they'd create. They probably won't be using the terminal. At least by 10 they're capable of it.