Everyone is an atheist until they do kernel/full system update on their daily driver machine
I still love the particular way that Garuda configures some things from the get go. I always knew it was Arch based and might break eventually. What I didn't expect was the stupid power button deciding that it doesn't want to work anymore.
pacman -Syu hangs after updating kernel but before mkinitcpio.
Jesus, take the wheel.
I just have a script that repeats the "install-kernel" command and the "bootctl install" one that I run after every big update. It should be fine without them, right? Too many times the kernel one fails in the pacman update chain and I've had to chroot from a live USB too many times to do the bootctl install to put the correct bootloaders in the efi partition to skip the manual bootclt install from my actual PC after updates.
Just in case. It takes 2 seconds vs searching the pendrive, loading, typing in an European keyboard when the live USB asumes it's american, searching the chroot command on my phone... All of this when I just want to relax. Weird stuff I know.
Me updating my Arch install in the morning at school (there's faster connection):
But, with current install I finally started writing logs of all manual changes I make (config updates, created symlinks outside home dir, package installations, etc...). I'll finally know what I did instead of trying to guess what weird thing I did 2 years ago.
True. I started to pray to GabeN recently too.
Let us pray that he will be succeeded by a worthy descendant. At least we can always find refuge in BSD - it has not yet started to ensh*tify as I've heard
chuckles in immutable distribution
Me, installing Linux mints major update like a month ago after finally getting things just right:
If it breaks, new distro I guess 🤷
Debian fans talking about how "rock stable" it is after I smash their computer with a rock:
Power button broke: Kalm
(True story: too bad it happened 2 days before finals)
I wish laptops were a practical thing when I was in school. I had a PDA and it was useless.
Mine was actually somewhat useful. (I was weird and used a windows mobile phone in HS because it was an upgrade over my nokia.)
Also the replacement power button broke after like two uses.
Last month I was doing some normal computer maintenance, and when I had gotten everything set up I found the computer wouldnt turn on. Took me a full week to diagnose the problem: it wasn't plugged into the wall.
These things can be so funny sometimes. My old PC from high school decided to die the exact day when I bought my new laptop. Mf won't boot up no matter what I did. Had to connect that hard drive to another machine to recover some data. Now I keep backups of everything.
This is what scares me with snapper.
It's reliable so I haven't had to figure out what to do if/when it does break.* Scurry thoughts *
I mean, snapper did its job. My hardware failed. I managed to get it going again by hammering the button with my finger.
I mean, Snapper did its job. My hardware failed. I managed to get it going again by hammering the button with my finger.
Yeah, I get that.
It's more that your post reminded me of another one I'd seen where someone didn't read one of those "advisories" before updating Arch. And Timeshift couldn't save them, so they had to figure out how to get everything up and running again.
If I recall correctly, they did get it running again fine, it just took a few hours. But I've been meaning to try and find somewhere to learn more about fixing failed boot, but the spartan grub prompt scares me, lmao!
I'm assuming Snapper can fail for the same reason Timeshift did for that guy.
Imagine how i feel installing dubious drivers in my qubes dom0.
quebeos is fairly well sand boxed, I thought - isn't that the whole point? I don't know much, but maybe you can break a while qube with a bad driver?
dom0 is the administration qube which handles the graphical desktop, i/o and hardware devices. So if you're installing dodgy software in dom0 you go around a lot of the sandboxing that qubes offers.
Well if it's a software issue you can just hold it down to force cut power.
Not software. Actual hardware hardware button.
Oh i assumed it was like most modern systems that a short press sends a shutdown command and a long press just cuts power
