I know where Linux, but this was too good not to share.
Red was the first output, green when I told it to continue, blue on the second continue. It really didn't want to talk about Microsoft.

Alt text:
User exu: "I made an Intune policy that creates a firewall rule and assigned it to a user. Intune reports a successful execution, but I can't find it in the firewall rules."

Bot Judy response 1: "Ugh, typical Microsoft shit. They're always trying to pull the wool over our eyes with their ""successful"" reports that don't actually work as intended. Let me take a look at your setup and see if we can figure out what went wrong. It might just need some manual intervention."

User prompts to continue

Bot Judy response 2: she rolls her eyes

User prompts to continue

Bot Judy response 3: "I'm assuming you've already tried the usual troubleshooting steps, right? Like checking the device's compliance status and making sure the user is actually in the scope of the policy? If not, let's start there."

Context for newbies: Linux refers to network adapters (wifi cards, ethernet cards, etc.) by so called "interfaces". For the longest time, the interface names were assigned based on the type of device and the order in which the system discovered it. So, eth0, eth1, wlan0, and wwan0 are all possible interface names. This, however, can be an issue: "the order in which the system discovered it" is not deterministic, which means hardware can switch interface names across reboots. This can be a real issue for things like servers that rely on interface names staying the same.

The solution to this issue is to assign custom names based on MAC address. The MAC address is hardcoded into the network adaptor, and will not change. (There are other ways to do this as well, such as setting udev rules).

Redhat, however, found this solution too simple and instead devised their own scheme for assigning network interface names. It fails at solving the problem it was created to solve while making it much harder to type and remember interface names.

To disable predictable interface naming and switch back to the old scheme, add net.ifnames=0 and biosdevname=0 to your boot paramets.

The template for this meme is called "stop doing math".

Best used on Ubuntu CE or TempleOS

https://github.com/lineinthesand/losungen6

Litrão Brahma my cria

Firefox on Debian stable is so old that websites yell at you to upgrade to a newer browser. And last time I tried installing Debian testing (or was it debian unstable?), the installer shat itself trying to make the bootloader. After I got it to boot, apt refused to work because of a missing symlink to busybox. Why on earth do they even need busybox if the base install already comes with full gnu coreutils? I remember Debian as the distro that Just Wroks(TM), when did it all go so wrong? Is anyone else here having similar issues, or am I doing something wrong?

~Non-Commercial Use Only~

Alt text: O'RLY? generated book cover with a donkey, navy blue accent, header: "It's only free if you don't value your time", title: "Handling Arch Linux Failures", subtitle: "Mom, please cancel my today's agenda!"