Found out the hard way that if you edit /etc/sudoers with anything other than visudo you best be absolutely sure the syntax is correct, otherwise sudo will refuse to read it and you’ll be locked out.
Also learned to add -rf to the rm command at the end, after I re-read it to make sure it does what it should do. Something like rm /path -rf instead of rm -fr /path. That protects you from your fat fingers hitting the enter key half way through.
Been there with sudo. Fortunately, su still works, as well as going to another tty and logging in as root. Well, as long as the root login is enabled; otherwise that old hack with init=/bin/bash may work, unless you’ve prohibited editing kernel cmdline in the boitloader or decided on efistub
Linux Mint: removed all taskbars from the desktop. I was hoping it would just allow me to reset them to the default. But in reality, it breaks the GUI and it’s very hard to reset from the GUI. Suddenly my keystrokes weren’t being detected and I couldn’t open up applications with any sort of regularity. After a lot of dicking around, I got the terminal working so I could reset Cinnamon.
It’s not the worst way I’ve broken a machine. But it was one of the most annoying.
One thing I learnt a while back is that if you break your GUI you can always use Ctrl+Alt+F<1-9> to go to different terminals to try to solve it. Worst case scenario I would do something like mv .config .config.bkp and sudo systemctl restart that should hopefully get you back to default settings on the UI.
Source: been there, done that. Not exactly your error but similar enough.
I once deleted the network system in alpine. I’d been having some trouble with with the default one (I think wpa_supplicant) so I decided to try the other one (I think iwctl). But I thought that there might be problems with havung both of them so before I installed iwctl I deleted wpa_supplicant (thinking that it was more of a config utility than the whole network system), only to find that I couldn’t connect to the internet to install iwctl.
First time trying Linux I went with an arch install because I Googled “best version of Linux” and went with arch. Followed a guide to the point of drive formatting and I decided to go with a setup with drive encryption. I didn’t understand what I was doing, ended up locking myself out of my hard drives and couldn’t get windows to reinstall on them. I used a MacBook for a week until I installed Ubuntu and managed to wipe and reset my drives and reinstalled. Needless to say I am going to read up a little more before I try that again.
Archinstall python script is your friend 😄😉 I tried install arch manually, but as I learned that not even sudo is included in the Linux essential packages, I stopped the process and went back to aromatic script install, lol, got no time for that S*** 😂
I have a stupid one, but far from funny… I’ve been using and building computers for a very long time so I’m far from a noob, but I’m still quite cautious, bordering on paranoid, so I like to unplug all other drives when re/installing an OS just to avoid stupid mistakes. I go through the installer on the livecd, there’s only one drive to choose from so I don’t think much about it, select that it should erase everything, I set up the new partition structure, and start the process. After about a minute I begin wondering “why is it taking so long?”, and “what is that ticking noise? SSDs shouldn’t be making any sounds when written to”, when I realize that I had unplugged the wrong drives and that I was currently overwriting my main storage drive. Of course I had backups of the most important things like photos and code, though not really synced for a couple of months so I lost some stuff permanently.
I used to be constantly making tweaks to stuff and distrohopping like none other, but in 2018 I finally found THE setup and settled down. These days it’s all about having scripts that set things up exactly how I want them.
Daaem, I guess the poor dude at the receiving end did not consider it particularly fun. Well, at least they had sbin working, so probably possible to recover without a live cd. Huh, guess who’s now spinning up a VM to check it out 🤣
Checked it out: on arch that results in inability to run tty on reboot, then you’re dropped into initramfs’s rescue shell where you can simply +x new_root’s /usr/bin/* and be back up and running
This is where someone tracks down an upgrade path chart you didn’t know existed and points out some goofy intermediary release, not an lts for some reason, that you were supposed to upgrade to first…
My laptop is the same except, I keep a Windows partition because the RGB keyboard controller is only available in a Windows app. That Windows partition exists in a post apocalyptic dystopia where Windows belongs; it has never, nor will ever see the internet. It is blocked my my network firewall. Windows is like a less than useful bootloader options tab.
Don’t know, but I’d just try it out and see if it works. It detected my motherboard, mouse, keyboard, everything. It was just such a relief after trying and failing to get the stock (windows only) software on linux running
Thanks for the suggestion. I’ll look into it. I’m a bit skeptical because the changes made in Windows are persistent, the secondary function keys give quick access to some of these features (but only 3 course brightness PWM settings for RGB), but mostly because there is a device on the USB device tree that is unknown to the Linux kernel on mainline-fedora.
Maybe there is some kind of kernel configuration option that just needs to be added, but the bootloader rejects custom keys generated for secure boot. Without my own keys I’m stuck with the shim and can’t run my own signed kernel. It might be possible to set the keys by booting into UEFI with Keytool, but my motivation hasn’t carried me that far into the problem yet. I could be wrong and the unknown USB device could be unrelated, and openrgb could work. Thanks again.
It will depend on the specific hardware, but I can vouche for openrgb. It works for me g502 hero mouse, and my asrok mobo/aio coolers fan RGB. Infact, I have more options than the motherboard gives me lol.
I have to keep a Windows install around for the sole purpose of pushing firmware updates to my Headrush pedal board. The installer will run on Linux with Wine, but it cannot detect the pedalboard through the USB connection.
Try giving this a try. I found it suggested in the Arch wiki to update the bios. It’s basically a bootable Windows environment from a USB. You can then try running your firmware updates through it. It worked to update my bios so I assume it should easily work with updating firmware for other devices.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.