i broke debian on my plex server and said fuck it and migrated to endeavor because im more familiar with arch
Linux
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
It do be like that, at least for the first couple years, and typically with decreasing frequency.
I'm on my second install now. I fucked up the first one pretty handily by accidentally wiping the boot partition in gparted. (Like a complete idiot, because the partitions are labeled.)
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.
Not sure you can fully brick a PC. Simple BIOS update and your back to scratch load an OS and go again. Hardware failure. That's where the bricking happens.
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 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
Once you break it a few times, you start to understand the value of btrfs or ZFS snapshots.
1
Both, to the point it doesn't boot, and just tweaking enough bugs that it's easier to jist start over.
Reply fail?
Just did a fresh install after attempting to migrate from a proxmox VM to baremetal (turns out my mobo only supports UEFI and after spending an hr trying to convert I just gave up and reinstalled)
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.
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 just spent 11 days on a dual boot repair in fstab, passwd, loads of ecryptfs, amongst other boot and login issues. Before restoring from the full system backup after getting mad to finally want to use my PC. 11 fucking days almost all day in terminal. TOO many partitions and too many folders inside of folders to get to my ecryptfs files. I got so lost LSing around.
After it all though, and it was an aneurism and a half. I still want to finish my goal and reinstall my dual boot this time correctly aiming the folders correctly.