“The impact of exploiting these vulnerabilities includes remote control of compromised servers, remote deployment of malware, ransomware and firmware implanting or bricking motherboard components (BMC or potentially BIOS/UEFI), potential physical damage to servers (over-voltage / firmware bricking), and indefinite reboot loops that a victim organization cannot interrupt,” Eclypsium said.
My guess is something is hanging or not configured correctly. Like a mount or a networking device or something. It will sit there and retry a bunch before moving on.
PopOS lets me hit escape during the boot process and see a live view of whats happening. I don’t know if that exists on Manjaro. Otherwise, you can look at /var/log/boot.log to see if something’s failed (it also might save in boot.log.1, boot.log.2, etc).
@Kruemel@feddit.de 's advice seems cool but I’ve never tried that before.
thanks, the pic is very clear and easily digestible. it seems that plymouth-quit-wait.service takes the longest (~23s). if i understand correctly, plymouth is essentially just some boot animation. is it a good idea to remove/disable/skip it?
edit: curiosity got the better of me. after following the steps described here, i have managed to remove the fancy plymouth boot animation and went from 40-ish seconds to 20-ish. good enough for me. cheers!
Not op but I lived with a younger nephew for some years. He looked up to me in every aspect and if I introduced him to something he would learn it to talk about it later. I unfortunately just introduced him to League of Legends, I was too young and wasn’t into linux myself.
I recently ordered a Brother printer, and it just works. “Brother MFCL3730CDNRF1” At one point it was a bit tricky to add it to Cups, but after it, it worked flawless.
linux
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.