Na, nothing. Did an update today. Nothing bad happened at al, Because why would it?
linuxmemes
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 users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- 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.
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
sudo
in Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
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 remove France.
still read βunattended updatesβ as βunintended updatesβ β¦
Windows does both
It doesn't. It will require you to reboot for every god-damned line of code that has changed.
I swear I heard my PC wake up in the middle of the night on its own several times, back when I used to run W10 on bare metal - god knows what it was doing
Firefox kept crashing because of explicit sync. Nothing new for an nvidia user such as myself. Still never going back to xorg.
Set MOZ_ENABLE_WAYLAND=0 before starting Firefox and it doesn't crash anymore
Thanks! If it gets annoying I'll give it a shot.
God, I love Read-only Friday where nothing bad ever happens before the weekend.
Speak for yourself. I am preparing for a high school camp on Monday and all our sound system isn't working. Stupid proprietary crappy sound boards.
Bless your heart.
I've found it funny how many people think they need to defend windows by saying " this could've happened to Linux too!!"
Okay, sure. Yeah you're right about Linux being just as insecure as windows too π
I think people are missing the point here. The biggest problem was not that the update was bricking the machines, that could've happened to Linux/macOS/BSD etc. The problem is that the solution to the problem is to MANUALLY access the machine, get into safe mode and type some commands. This is insane. And you should be able to EASILY disable automatic updates for apps like that on Windows Server.
I dunno, I'd say them deploying an update that bricked machines at the scale they did shows they didn't test it very well at smaller scales. They could have even still used their users as beta testers, just needed to do a subset of them first.
Crowdstrike exists for Linux. Are their reports their update affected Linux servers? I have not read that anywhere.
Something similar did happen on Linux clients with CrowdStrike installed not too long ago lol
Sounds a bit like its a bad idea to install CrowdStrike regardless of the system π
checkbox compliance β companies are required to have something in place that checks the box so they can pass the audit
lol yeah thatβs a glowing review.
βOh, we can fuck other shit up too!β
Anything to defend windows
Noone needs to defend Windows. We need to defend the truth. And the truth is that this was not a Windows issue. It's a Crowdstrike issue.
Windows being an insecure shit show is no one else's fault though. Not sure why that draws an argument. It's well known
True. But nothing to do with this incident. That's the point.
Everything to do with it. You don't buy expensive software to protect your shitty OS unless it's a shitty OS
To those many Linux users who took a look at their circumstances and said "I definitely need antivirus software!"
CrowdStrike does more than anti-virus and yes enterprise Linux installations need a lot of security controls that average Linux users don't need.
Yeah but 14th Gen Intel CPUs are still failing regardless of your OS.
Proudly an AMD user for 25 years now :)
Even bulldozer?
Nobody but the most hardcore AMD enthusiasts used Bulldozer. The 2010s was a tough decade for AMD, to say the least. It wasn't until AM5 came out that I finally switched back to Team Red. Got too used to LGA sockets.
I still don't know why they thought sticking with PGA was a good idea... The amount of processors that were ripped out of their sockets is insane
not familiar. Their processors tend to last me ~5 years so it's not like I bought every model available
Nothing much, just getting far fewer client emails for some reason...
https://www.abc.net.au/news/2024-07-19/what-is-crowdstrike-outage-explained/104120260
This has happened and taken a bunch of services down around the world.
What a garbage.
Just use Linux, SELinux, strong sandboxing, repositories, nonexecutable home directories, strong access control, offline backups.
How about a testing environment separate from production
and phased rollouts β¦
I watched a ocean of computers go dead on the floor because I couldn't convince the sysadmin to do exactly that when pushing a major change.
Any more details?
This sounds like the setup to a fun story.