aka @JWBananas@startrek.website aka @JWBananas@lemmy.world aka @JWBananas@kbin.social
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”
Beep tha boop outta here
Exploding drones. They’re basically ordinance.
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?
They confiscated the portal tech and shipped it away in crates marked classified and with the Daystrom Institute logo.
Wesley said Solum needed to invent that tech so that the Protostar could be sent back in time. So the Federation clearly didn’t have anything like it yet.
What are the odds this is the precursor to the portal tech stolen and used by Vadic in Picard season 3?
How were they able to reunite with Voyager without triggering the Living Construct?
Edit: Never mind, they lampshaded it in the next episode.
In 2x01, yes.
Live logs and proper
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.
Is it not the set from Strange New Worlds? Saves on budget?
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.
Way better than Patrick Stewart at 83.
You just described most of my experiences with Uber
pihole*