Banning CFCs went pretty well too

or my CPU, which kind of doubt

Not a 13-14 gen Intel, per chance?

It reads very “if it ain’t broke, take it apart and fix it”

Nobody:

Crowdstrike:

Sysadmin here. Wtf are you talking about? All we did was “rapidly fix the issue by disabling Crowdstrike module.” Or really, just the one bad file. We were back online before most people even woke up.

What do you think Crowdstrike can do from their end to stop a boot loop?

E.g. why do you need more than 2 years of support for a workstation?

Enterprise isn’t rolling out the new release on release day.

Enterprise is waiting until the “.1” release so that the most glaring bugs can be identified and resolved. And enterprise is doing gradual rollouts after that, with validation, training, hardware refreshes, etc.

For a release with only two years of security updates, it would not be surprising for a given enterprise to only have the chance to take advantage of, at most, one year of them.

A two-year LTS release cadence with a five-year tail of support and security updates is much more practical. That leaves enough overlap in support for enterprises to maintain their own two-year refresh cadence without having to go through periods without security updates and support.

Stating that debian isn’t secure enough really confuses me as it is one of the most solid distros out there.

Where is the toggle to enable NIST-certified FIPS compliance in Debian? On Ubuntu you just enable it using the pro client and reboot.

It would have been BackTrack Knoppix back then. And even that wasn’t released until 2000.

The script-based systems came first. They had to evolve into the amalgamation of pitfalls that they have become for someone to abstract out their important concepts into something that could use configuration files.

Calling it tsusers just feels wrong