This is how I use it in my bash script:

  current_ip=$(curl -s -X GET https://1.1.1.1/cdn-cgi/trace | grep -Po "(?<=ip=)(.*)")

I find awk more clear for this kind of job. You can replace

  grep -Po "(?<=ip=)(.*)"

with

  awk -F= '$1 == "ip" { print $2 }'

Thanks for that, I agree.

That's an interesting recommendation...

> We've received feedback from customers that several reboots (as many as 15 have been reported) may be required, but overall feedback is that reboots are an effective troubleshooting step at this stage.

https://azure.status.microsoft/en-ca/status

Why would multiple reboots make sense? I can accept three reboots triggering some condition that tries three times before it stops trying, but fifteen?

With my experience dating back to 286 machines, sometimes even kicking the box (literally) solves the problem

Put on yer “re-bootin’” boots !

They don't call them reboots for nothing.

Ahaha what nice memories you brought back!

Have you tried turning it off and on and off and on again?

It sounds like a race condition; you want the CrowdStrike updater to start and pull down the fix before the affected virus definition file is loaded and kills the box.

If you keep rebooting, you eventually may get those to load in the right order.

Sounds a lot like my work laptop's antivirus software, which gives me a total of two minutes of internet from within WSL2 before blocking it entirely.

I'm curious if you are sure it's antivirus? WSL networking is weird and can be a pain in the ass. Especially in VPNs are used.

I'm wondering if you know wsl-vpnkit?

Not familiar with this tool, sorry.

Anyway, had that confirmed by whoever is in charge of security and whatnot, as we have an internal StackOverflow clone and someone asking the same question was pointed to a PowerPoint presentation of dos and don'ts.

I see. For me it was worse with WSL1, where all file operations were scanned by slow enterprise DLP software.

Now with WSL2 most pains I see are related to broken routing when also using VPNs on host. That is where that vpnkit tool shines.

I've found disabling/enabling the virtual network bridge fixes VPN issues.

Of course in win11 Microsoft decided to make the bridge hidden for some unknown reason, so good luck figuring it out...

That's what I thought - it would have to be something probabilistic with a 99% chance within 15 reboots or so.

There was also a French Canadian version of this show called "Octo-puce".

https://fr.wikipedia.org/wiki/Octo-puce

That's an awesome name. ("Puce" is French for "Computer Chip" in this context, "Octo" as in Octet).

Today I learned that the "s" in SX means "single" and "d" in DX means double. The DX has double the data bus width of the SX (32-bit vs 16-bit).

But then the 486 DX has a floating-point unit, while the 486 SX does not. So Intel just went with DX is better than SX.

There were rumours that the DX and SX chips were exactly the same:

Intel zapped the FPU on the SX to disable it. Apparently it cost more to make, but sold for less.

The (80-bit) floating point in historic Intel processors is deprecated, FYI.

After the exchange of MMX and 3d-NOW, it was AMD that adopted Intel SSE into amd64.

https://en.m.wikipedia.org/wiki/Streaming_SIMD_Extensions

The 386sx was my first overclock switching time crystals out on the board.

Before TAOCP came The Art of the Organ-Builder

https://en.wikipedia.org/wiki/Dom_B%C3%A9dos_de_Celles?wprov...

The best tool I've used on Windows for that is "Scanner" by Steffen Gerlach:

http://www.steffengerlach.de/freeware/

WizTree is vastly faster than the other options presented here (Scanner, SpaceSniffer, WinDirStat).

WizTree v3.33 is the last 'donationware' version vs. free for personal use now.

https://diskanalyzer.com/wiztree-old-versions

Switched to this a few years ago. Far better than anything else I've tried.

It's also the one that's much more regularly updated.

I'm personally a fan of SpaceSniffer: http://www.uderzo.it/main_products/space_sniffer/index.html

While we're listing them, Disk Inventory X (https://www.derlien.com/)

Thanks for sharing! I really like the real time update during progress. You sometimes have to wait a very long time in Scanner before you see the result.

I find myself using WinDirStat on Windows systems, but often use ncdu in WSL.

On Windows, you should switch to WizTree. Rather than recursively calling directory listing functions, it directly reads and parses the file tables itself. This makes it orders of magnitude faster. I have a 2 TB hard drive full of a million files, and WizTree reads and parses it all in under a minute, whereas I can expect WinDirStat to take half an hour.

On an SSD, WizTree only takes a couple seconds.

For all the hate NTFS gets, MFT has led to the creation to two amazing tools: Everything and WizTree. Unfortunately both proprietary although freeware.

Thanks for the suggestion!

You should try Directory Report on Windows. It is faster than WinDirStat. Has more filtering and reporting than WinDirStat. Can find duplicate files too

I use WinDirStat on Windows

https://windirstat.net/

You should switch to WizTree. Rather than recursively calling directory listing functions, it directly reads and parses the file tables itself. This makes it orders of magnitude faster. I have a 2 TB hard drive full of a million files, and WizTree reads and parses it all in under a minute, whereas I can expect WinDirStat to take half an hour.

On an SSD, WizTree only takes a couple seconds.

`dua`, discussed elsewhere in this thread also works on windows, just for another option.

Simplifier's 4x4 includes both upper and lower case.

Yes, I was simply experimenting on how low you can go. I love small fonts! And Simplifier's one is clearly impressive.

Hats off to your experiment, it's still impressive :).

There's also the native Windows version of XTree: ZTreeWin (https://www.ztree.com/index.html)