Its all locked behind the CrowdStrike Support portal. Lucky a nice person posted on Reddit.
Thank you, sir!
Brought my entire gigantic multinational employer to itâs knees but lucky for me I like to keep my IT experience on the hush-hush and do it solely for pleasure, so I got to spend the day on the sofa infront of the TV occasionally glancing at my work phone to see if anyone had implemented the fixes yet. They didnât just have to stand our servers back up, but also the several thousands of users around the world who are mostly working remotely
A full dayâs pay to catch up on my shows, thank you crowdstrike!
If that were possible, I would have liked to be in vicinity of @dalto
One other thing for our IT professionals, at the end of June 2024 there was some sort of policy update and code change in CrowdStrike which caused the agent to consume 1 core of your CPU 100% sustained till:
- You received the policy update from your CrowdStrike tenant.
- Must reboot the workstation\server to regain the CPU core.
We experienced the problem for atleast 3/4 of the business day.
CrowdStrike presently has no LTS model. You will get the latest fixes + features when you get the next update from the CrowdStrike Tenant\Cloud.
Source:
Listen to the protip
I just want my OS to work. This isnât about getting info about something. You get info the way you best understand and can digest it. I was talking about OS stuff and frankly, things should just be made to work. I donât want to deal with stuff unless I absolutely have to.
Thanks to CrowedStrike I never went to work today, Oh I forgot, Iâm retired!
CrowedStrike for life
Then youâd probably be happier with a static release cycle where things are more tested and controlled.
You do realize weâre rolling, and thus testing is fairly minimal. There will be speed bumps and maybe even some crashes. Itâs wild out here!
Not too bad for me either. I work remote for a huge multinational. Just couldnât access the network drives in the morning, but things were mostly resolved for me after a couple hours.
You forgot about the voting machines! They went too! The never online voting machines!
Thatâs how it is with shared points of failure.
WeedStrike I wonder what itâs effect would be on Linux?
Rich;)
Nope. Quite the opposite. You see, I want a distro that is a rolling release, but the repos arenât updated as soon as possible when a package comes out. The maintainers and the community test out the packages and have some automated testing in place as well. I only know about OpenSUSE Tumbleweed doing this.
Manjaro fits well your description however Iâm not sure about the âautomated testingâ part.
Manjaro packages start their lives in the unstable branch. Once they are a deemed stable, they are moved to the testing branch, where more tests will be realized to ensure the package is ready to be submitted to the stable branch.
At any rate I hope you are content with openSUSE.
I do run Tumbleweed from time to time and it is a magnificent system.
Seen from another angle:
I actually moved back to Arch because I couldnât figure how to get mp4 codecs going on Tumbleweed. I then learnt that it was simpler than I thought to get them working, but I already set up everything on this new install of EOS, so Iâm not moving unless something bad happens on this current install of EOS. I will just wait a week before I update packages instead of updating them immediately.
When I was still a static-distro user, I saw a YT comment somewhere saying âwe should appreciate Arch users, as someone needs to beta-test our softwareâ.