Weirdly and oppositely this is actually how bees reproduce. Fertilized eggs become female, unfertilized become male

I just never left 100% native (apt in my case). I have been trying to make the switch to 100% flatpak…but it’s so painful that I just haven’t.

If this was here a week ago I might have rolled this out for April fool’s lol, I’m the domain admin for a small company and I’m pretty sure I could get away with it for the occasion, maybe if I remember next year

I still use them exclusively lol

resizepart 1 128 Instead of 128GiB …bad day

Oh god, as if I wasn’t scared enough about running a filesystem that got kicked out of mainline and is maintained more or less by a single dude. I’ll stick to btrfs thanks

Yes I know, I was gonna say “shell is confused” but it just didn’t feel like it had the same ring to it

Bash would be confused

Took them long enough, eclipse has only had this for like a decade at this point

Same although for a totally different reason. There are some services that really don’t like gtlds and they will say your address is invalid if it doesn’t end in .com, .net, or .org…all my serious domains are gtld…so some services have emails on meme domains because the only domains I have with traditional tlds are memes

No not really, I just don’t like having the address on my interface, ironically it doesn’t break half the stuff that removing 127.0.0.1 does…but I do that too XD. Removing loopback isn’t actually THAT bad but I’ve found more stuff that struggles with that than with not having a clat

I deliberately don’t want or use a clat, the goal is to avoid IPv4

It’s gotten better but I’m not v6 only, I just don’t have v4. I have NAT64 which basically uses your IPv6 as the private address in a traditional NAT setup, allowing you to continue to access the legacy internet without IPv4 inside your network. Catch is you can’t connect to IPv4 addresses because it relies on a DNS64 server to generate IPv6 AAAA records from the IPv4 address when a domain only returns IPv4 so only DNS based services work. Basically it lets you have all the befits of a v6 only network with few of the drawbacks.

…right…I can’t view this meme LMAO…I don’t have IPv4 on my network 🤣

Too bad it doesn’t work, probably because of vhosting

Yep, I’m aware of that too, doesn’t change my initial point

…right…tell that to cmd.exe or the OpenVPN daemon, or the soft ether VPN daemon, or OpenConsole.exe, or Idk, I only tested 4 that immediately came to mind but my point stands. There are a lot of programs that do not have a window handle and do not bother with window messages.

You clearly didn’t read my message…I said a “window close message.” I.e…WM_CLOSE. that is not a process signal, it’s a window management signal. Hence taskkill not working without /f on headless processes

TIL about the console signaling stuff, good to know. I am aware of SEH but that seemed a little too in the weeds for this discussion since that’s as you say akin to SIGSEGV

Ironically it’s actually the opposite. Linux has signals, and with the exception of SIGKILL and I think SIGABRT they can all be handled gracefully. Windows on the other hand doesn’t have signals, it can only TerminateProcess() which is forceful. The illusion of graceful termination on windows is done by sending a Window close message to all of the windows belonging to a given process, however in the event the process has no windows, only forceful termination is available due to the lack of a real mechanism to gracefully terminate processes. That’s why the taskkill command tells you a process requires forceful termination when you run it against something headless.