278
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 Jul 2024
278 points (93.2% liked)
Showerthoughts
29525 readers
726 users here now
A "Showerthought" is a simple term used to describe the thoughts that pop into your head while you're doing everyday things like taking a shower, driving, or just daydreaming. A showerthought should offer a unique perspective on an ordinary part of life.
Rules
- All posts must be showerthoughts
- The entire showerthought must be in the title
- Avoid politics
- 3.1) NEW RULE as of 5 Nov 2024, trying it out
- 3.2) Political posts often end up being circle jerks (not offering unique perspective) or enflaming (too much work for mods).
- 3.3) Try c/politicaldiscussion, volunteer as a mod here, or start your own community.
- Posts must be original/unique
- Adhere to Lemmy's Code of Conduct
founded 1 year ago
MODERATORS
Probably not. Most Linux admins know their systems and are able to navigate out of the situation with ease. But also most people don't use any corporate off-the-shelf software, because there are better options that are freely available.
Furthermore a Linux installation is dedicated and slim for one single purpose. The flexibility creates diversity.
Are you implying that Windows server admins don't know their shit?
I've scene some supposedly 20 year veterans who don't know the architecture of AD
Not to say that is all of them but I've scene some who really can't do anything outside of click some buttons.
No. They don't. They always need Microsoft support to solve situations and upgrades. You can also ask simple questions that they cannot answer. Try Active Directory: how to run AD in a secure fashion? Or: What services do rely on DCs in our company?
My guy, I work cloud support for both Linux and Windows VMs.
I get dumbass cases from both all the time.
As a Windows engineer, the number of times I've seen other "engineers" open a case with Microsoft is insane. It seems to be a lot of their first reactions. No logs, no trying anything, just "this broke, why no work". I think it's that the Linux guys are mostly self taught, and the windows guys aren't.
I think it's more of "we pay Microsoft (or any company) for this. Make them handle it."
It's that kind of thinking that makes shit like the crowd strike problem possible.
Windows server admins: "We pay Microsoft for the service, damn right we'll use it!"
Linux server admins: "We don't pay anyone for the service, hopefully someone else had the same issue and posted about it somewhere..."
Interestingly, the latter ends up with better stability and security!
I think the shower thought is centered around IF a ubiquitous bug that required physical access to the machine to resolve occurred simultaneously across all Linux machines.
If you couldn't remotely resolve the issues, regardless of your competence, simply the WALK to each machine and hooking up a KVM to each one would take a long time.
Connect to your hypervisor remotely, pray it uses something like bhyve/FreeBSD
There won't be such case is my argument. No one patches a system "for fun" and automatically there except they really set it up like that. It would be only one kind of a case in one company.
Furthermore, you cannot compare Linux systems. A modem firmware with busybox is not the same as a Debian PC desktop. It works differently and has only the kernel in common. And in both cases they aren't patched at the same time. They are not even the same version, hell not even the same platform.
E.a. nothing will ever break like this. If it does, it will be one single case of a single IT department.
This combination of arrogance and complacency sort of thinking is how it does happen on Linux one day.
Linux also isn't as popular on the desktop or end user devices