this post was submitted on 07 Mar 2024
1412 points (92.9% liked)
linuxmemes
21355 readers
1604 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've seen an entire factory shut down for hours because two critical Win10 computers tried and failed to update. It's never an issue until it becomes one.
Plus a failed update is the whole reason I nuked my C: drive and switched to Manjaro (now running Arch, put down the pitchforks).
Well, running Windows 10, a consumer user-oriented operating system, to control mission-critical machines is mistake number 1.
This wouldn't have happened if they had used Windows Server or something actually designed for that task (like Linux!).
Neither of those options were available. It was written by a third-party for some old .NET Framework version, and the server and GUI components were written as a single application. Putting it on a server wasn't an option either because the application's GUI was constantly used for the management of assembly machines, and other applications were used for monitoring and administrative stuff.
If you had been there, you'd know why this was a low-priority risk. That place was bleeding from a thousand wounds. At least this had some redundancy, for all it was worth in the end...
(edit) I actually contributed to that software, even though it's not open-source! I managed to nail down an issue where loading a project file using one locale would result in a crash, but not in others. The .NET stack trace was printed to an XHR response's payload and I used that to locate a
float.ToString()call whereCurrentCulturewas passed as the cultureInfo instead ofInvariantCulture, so depending on the computer's locale, it would try to parse CSV data either using a decimal dot or a decimal comma. I mailed this to the maintainer and the fix was released within the month.Windows Server is an option.
The operating system is called "Windows Server". It doesn't necessarily have to run on a mainframe. It has the regular Windows GUI (with a few differences, the first you'll notice is "Cntr+Alt+Del to log in") and can run regular Windows programs.
Or even just running the critical machines offline
Huh... I wonder why there's versions of it called "Enterprise" then. You might want to talk with Microsoft about their clear mistake. I mean clearly https://www.microsoft.com/en-us/microsoft-365/windows/windows-11-enterprise is in error since you're correct right?
I work in IT. Windows 10/11 Enterprise is still a bad choice. If it's a mission-critical system and you must choose Windows, pony up the cash for Windows Server.
The difference between Windows Enterprise and Pro/Home editions is that there are features on it that make my job easier, but it's still the same shitty operating system under the hood. Windows Server is much more robust and reliable in my experience. Still shit, but slightly less so. It's designed to run on machines with 24/7 uptime. Windows Enterprise still expects you to regularly restart it for updates and upgrades. That's alright since we can just set Susan from Finance's computer to update at 03:00. It's not okay if that computer controls the entire factory.
I too work in IT... Just because I have some HR users that need to run Quickbooks, I don't buy them Windows server 2022.
Well, QuickBooks is hardly "mission critical" (usually) although its "server" functionality is so jank that it's an entirely different discussion.
If you have sufficient outage that paychecks don't get cut... it will turn mission critical pretty fast.
You're not going to have a multiple-day outage. At most, it'll be a few hours.
If your company isn't printing out paycheques and payroll advices at least a day before payday, and is instead waiting until the last minute, that represents an organisational failure, not a technical one.
Edit: And don't forget... the manager can always write the cheques by hand on a paper chequebook.