arapaho boosted
Welcome to 2019, traveler from 2009. The brief:
-sysadmins are now "ops"
-servers are all just "cloud" something
-algorithms are "AI"
-DBs are "blockchains"
-Everything that spies on people is "smart"

Good luck. And update your CV with the above words.
arapaho boosted

management tools simply has become a way to replicate and execute atrocious scripts across multiple systems - not a way to create sensible systems management.

So yes, I will confess to being a PITA when it comes to sysadmin, to keeping machines a version behind to make sure they are stable, to pondering over patches before committing and, overall, security is a byproduct of proper sysadmin where you actually know your systems and can depend on them.

arapaho boosted

proper sysadmins "took too long" to do stuff for the developers who clearly a) know best and b) are in a hurry to deploy their marvels.

Net result is that I have started seeing stuff no competent sysadmin would ever do in production: machines where the ownership of / has been changed by rogue untested scripts, configuration files which do not survive reboots because they have been mangled by yet another creative script and so on.

What amazes me even more is that devops using ansible or other…

arapaho boosted

whole department to which people connected over serial terminals: no space for going cowboy.

In many ways I never lost the habit except the bit about having printed copies to pour on because now we have VMs on which to test before going into production.

I have therefore a profound issue with devops which appears to be "do sysadmin like you do dev" which, these days, seems to be approximately the same as "just test in production".

What is worse is that devops has apparently appeared because…

arapaho boosted

a bizarre machine on DECnet years later (by then we had moved to BSD and TCP/IP). We, the young guns, would sit around and listen to the incantations which she (yes, a woman, back in the 80s they, more than one, ran the university systems) suggested as a fix as her colleague would debug it "live" putting in, *by hand*, an address and working through the rulesets to see what would happen.

Nobody dared change anything without a long manual examination progress. There was one machine for a…

arapaho boosted

History time…

When I was taught system administration there was one and only one keyword: "stability".

Except for the "development" machine, where they were tinkering with Unix Version 7 source code, nobody was to perform actions on the system without understanding the impact they might have and without checking the log book.

I remember the time it took to modify the file: there was a printed copy of the "live" version and the Sendmail guru would ponder how to add a rule for…

arapaho boosted

@athoune @Keltounet Zero would be better. Operating systems already have package managers. Because users don't care about the language used, language-specific package managers are a bad idea.

arapaho boosted
arapaho boosted

Enfin des chiffres intéressants sur la coupe du monde de foot

arapaho boosted
Scenario 4)

A company takes an entire BSD OS and makes it a core part of their product.

If they don't upstream their changes they're royally fucked. This has happened to many corps. They get stuck on ancient OS releases full of vulnerabilities and other issues.

The smart vendors send their changes upstream, because when we make massive changes to our kernel they don't have to rewrite their code. Instead they get our improvements for free. It's a win-win situation.

The GPL argument is greatly exaggerated. GREATLY.

BSD code creates standards because corporations will use that reference implementation. This is a good thing.
arapaho boosted
Scenario 3)

BSD code is taken and greatly modified, becomes part of a commercial product. It's probably a tiny library not worth a lot or they'd cooperate with upstream to ensure they don't have to maintain the code forever because that's expensive.
arapaho boosted
Scenario 2)

BSD code is taken and modified to work with proprietary hardware that nobody else will ever have access to. We don't want their code. It's useless to us. Keep it out of our tree.
arapaho boosted
Scenario 1)

BSD code is used by a corporation and altered in a way that nobody else would require. We'll call this the Netflix Model. They did very interesting things to the TCP/IP stack for performance (jammed in TLS in the kernel like Solaris used to have, hacked things so badly it breaks IPSEC, etc). They actually tried to give the code back, we told them no because we don't want it there by default and we don't want a kernel module with a corporation's name on it. Nobody else should ever use this.
arapaho boosted

@cynicalsecurity It is an Open Compute Yosemite backplane with four single-socket Monolake SoC server boards sharing a 100G NIC via SR-IOV.

arapaho boosted

With the surge of new masto-friends, lets bring back #ff or #followfriday.

Who would you like others to be following?

Boosts appreciated, will boost replies.

arapaho boosted

I have created a #Librepay account for donations to me. I intend to use any monies to cover my open-source work, and for hosting this instance.

Since donations through the service are anonymous, I don't know if, or how much, people have donated.

arapaho boosted

2000: your conversation medium is a standard protocol with a native client on every platform
2010: your conversation medium is a website
2015: your conversation medium is a web app
2017: your conversation medium is an app only available on Android and iOS

GVA airport + 3 snowflakes == closed. The only airport in the world to do this. Never seen this in Berlin, Oslo or Helsinki. This Geneva area is a shame every time it's snowing. Sick of it.

Show more

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!