

That explanation is also the first paragraph of the article you’re responding to btw.


That explanation is also the first paragraph of the article you’re responding to btw.


Did the problem begin right after a kernel upgrade? Slim chance, but only thing I can think of is maybe some module your boot process depends on is no longer built-in the kernel and needs to be added to initrd manually. I always have an LTS kernel installed as backup to be able to exclude these kind of fucky issues.
If you don’t have an LTS kernel installed, you could try to boot a live usb, chroot into your EndeavourOS installation (don’t forget to do a mount -a inside the chroot environment to mount boot and efi partitions) and install the LTS kernel. If you’re able to reboot with an LTS kernel that makes debugging a whole lot easier.
Best of luck.
(The ‘shorter uuids’ are probably the vfat boot and efi partitions btw. Maybe you have access to lsblk or blkid in rescue mode to give some hints? You could compare them to live usb outputs of those commands)


US embassy warns of unintended consequences
Captain subtext: Nice [thousands of Irish jobs] you got there, would be a shame if something happened to them.


government controlled subsidized


Ah yes. America, famous for its diplomacy.


If it’s Russian windows I’d at least expect a wallpaper of a guy being autodefenestrated by some dark figure.


Systemd
*grabs popcorn*


Nah man, piece of shit software; Sometimes it just lists some random directory contents.
Not a dig at you or the script author, but I’m kinda miffed we’re relegated to running some rando github user’s bash scripts to check if we’re affected. This is the direct opposite response one should have to this kind of attack. I feel the AUR maintainers should have been more forthcoming about what they are doing to stop the attack and how users can mitigate the consequences if affected.


Professional shit-stirrer stirs shit. Nothing to see here, move on.


Yeah sure, we’re the reason you can’t get cock off your mind.


Without wearing a raincoat.


Because Iran doesn’t have the authority to ban Israel.
(But I guess you haven’t read the article.)


“It’s being towed beyond the environment”


Duke Nukem Forawhile
*would have
We almost have the same setup then, I use
ssh_hostnames=$(grep "^Host " ~/.ssh/config | awk '!/*/ {print $2}')
for host in $ssh_hostnames
do
alias $host="ssh $host"
done
in my .bash_aliases to parse the ~/.ssh/config file and cut off the 'ssh ’ part automatically for every Host I have in there.
United Arab Emirates only moving its ass in the right direction after involvement from the US should be remembered and held against them when they’re in a position of need sometime in the future.