I would actually be amazed if I ever bricked a PC fucking around with installing software to it. At the very worst, I might have to move a jumper pin to flash the CMOS and start fresh like I never even touched the thing. If somehow even that fails, it would be a unique experience.
this post was submitted on 20 Mar 2025
309 points (97.5% liked)
Linux
54952 readers
544 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 6 years ago
MODERATORS
I always think of Kiwi / Ozzie slang when I type chroot.
Of course that's after consulting the ArchKiwi to remember how to mount it
Ah Chroot bro
Maybe 1 or 2 back when things were less stable, but any time I have used Linux in the past 7 years or so, and particularly since I started using Debian as my primary OS, I haven't had any problems outside of trying to get some windows applications to emulate correctly, and one time when I echo'd into sources.list with > instead of >>. Anything else is just stuff I had to learn, like my boot folder filling up with old images that have to be cleaned out occasionally.
If you want shit to just work when you want and stay out the way when you aren't using it. Debian of whatever source is what they call stability. I've done rolling, and bleeding edge. It's all a constant pain. Becomes a job to maintain or bug track or check logs. I'll never go back.
load more comments
(1 replies)
Both, to the point it doesn't boot, and just tweaking enough bugs that it's easier to jist start over.
Reply fail?
Once you break it a few times, you start to understand the value of btrfs or ZFS snapshots.
load more comments
(2 replies)
Bricking hardware is a form of enrichment for me.
Ah, have you found the land of IoT? Bricks everywhere, you'd love it.
You're suggesting I should follow the yellow brick road to find the Wizard of iOT?
Why not... or try another brick in the wall
I haven't had any issues with the kernel yet. The worst thing that I can remember doing is messing up the systemd boot entry on my Arch Linux install.
I learned by a lot of distro hopping, tweaking and tuning and compiling kernels (way back when tho), to not being afraid of "breaking things." Since Nov. 1992. It helps when you use a spare PC or laptop though, no panic about loss
I've never in 15 years of Linux use and tinker have ever screwed a kernel. And I compiled LFS once.
Nearly always it's been during the live USB install of a dual-boot that a distro messes with the grub or installed grub to the USB disk itself. The fault lies with me because I'm almost blindly trusting the distro, but also with the distro for lacking proper yet succinct documentation during the install or configuration of partitions.
I am very happy I am doing this on a ProxMox machine. So fast to flip them up again