It would have been BackTrack Knoppix back then. And even that wasn’t released until 2000.
aka @JWBananas@startrek.website aka @JWBananas@lemmy.world aka @JWBananas@kbin.social
It would have been BackTrack Knoppix back then. And even that wasn’t released until 2000.
At this point the sheer complexity is too much of a barrier to entry. You are talking about centuries of man-hours to even approach par.
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.
I read it as “Wraith Flags” and wondered how Colonel John Sheppard has been doing.
Way better than Patrick Stewart at 83.
And the other 40 kept it quiet
Calling it tsusers
just feels wrong
People like to say that Kirk is the reason that the rules are so much more strict for Picard.
But Archer is the reason that they’re so much more strict for Kirk.
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.
Where is the toggle to enable NIST-certified FIPS compliance in Debian? On Ubuntu you just enable it using the
pro
client and reboot.