BonesOfTheMoon@lemmy.world to linuxmemes@lemmy.world · 5 months agoWhat's going on y'all?lemmy.worldimagemessage-square93fedilinkarrow-up11.27K
arrow-up11.27KimageWhat's going on y'all?lemmy.worldBonesOfTheMoon@lemmy.world to linuxmemes@lemmy.world · 5 months agomessage-square93fedilink
minus-squareboredsquirrel@slrpnk.netlinkfedilinkarrow-up18·5 months agoWhat a garbage. Just use Linux, SELinux, strong sandboxing, repositories, nonexecutable home directories, strong access control, offline backups.
minus-squarebobs_monkey@lemm.eelinkfedilinkarrow-up28·5 months agoHow about a testing environment separate from production
minus-squareToes♀@ani.sociallinkfedilinkarrow-up11·5 months agoI 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.
minus-squareGestrid@lemmy.calinkfedilinkEnglisharrow-up3·edit-25 months agoAny more details? This sounds like the setup to a fun story.
minus-squareRevan343@lemmy.calinkfedilinkarrow-up5·5 months agoBest I can do is push it worldwide on a Friday morning
minus-squarepeopleproblems@lemmy.worldlinkfedilinkarrow-up1·5 months agoYes. And time. We make a lot more money by testing in production, and let the users tell us what’s wrong. It’s much faster.
minus-squareluckystarr@feddit.orglinkfedilinkDeutscharrow-up3·5 months agoWe’ve successfully replaced the entire support team with an HTML form creating tickets for the one developer. Surefire way to receive that efficiency performance bonus.
minus-squareToes♀@ani.sociallinkfedilinkarrow-up9·5 months agoBut how do I integrate everything into Microsoft 365 with that snazzy OneDrive feature? /s
minus-squarejaybone@lemmy.worldlinkfedilinkarrow-up4·5 months agoYou will escort us to sector zero zero one.
minus-squareWordBox@lemmy.worldlinkfedilinkarrow-up8·5 months agoCrowd strike did this to Linux in April.
minus-squarebulwark@lemmy.worldlinkfedilinkEnglisharrow-up1·5 months agohttps://access.redhat.com/solutions/7068083 interesting it uses eBPF.
minus-squareXanvial@lemmy.worldlinkfedilinkarrow-up8·edit-25 months agoPretty sure it’s happened in Linux before, but because it’s much less users, obviously it won’t have same global outage like what happens now
minus-squareboredsquirrel@slrpnk.netlinkfedilinkarrow-up1·5 months agoI mean, I run Fedora and ran many others and had multiple crashes. Fedora Atomic Desktops not anymore, but still not perfect.
minus-squarePossibly linux@lemmy.ziplinkfedilinkEnglisharrow-up3·5 months agoAnd log monitoring with off machine collections
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 …
And my axe
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.
Best I can do is push it worldwide on a Friday morning
Does that cost money?
Yes. And time.
We make a lot more money by testing in production, and let the users tell us what’s wrong. It’s much faster.
We’ve successfully replaced the entire support team with an HTML form creating tickets for the one developer.
Surefire way to receive that efficiency performance bonus.
But how do I integrate everything into Microsoft 365 with that snazzy OneDrive feature? /s
You will escort us to sector zero zero one.
Crowd strike did this to Linux in April.
Damn
https://access.redhat.com/solutions/7068083
interesting it uses eBPF.
Pretty sure it’s happened in Linux before, but because it’s much less users, obviously it won’t have same global outage like what happens now
I mean, I run Fedora and ran many others and had multiple crashes.
Fedora Atomic Desktops not anymore, but still not perfect.
And log monitoring with off machine collections