Linux users online tend to get very high and mighty every time another OS has a sucurity bug. But it’s a good thing for Linux hehe
That’s because illuminating security vulnerabilities is VERY GENERALLY a good thing for an open source community driven software that can be more agile than closed and private code bases that are GENERALLY entrenched in a corporate structure slowed by all of the inertia inherent in those systems.
This process initiates with Linus Torvalds, wherein, he releases a new kernel and then opens a 2-week merge window. During this merge window, he pulls the code for the next release from subsystem maintainers. Subsystem maintainers send signed git pull requests to Linus either during the merge window or before
I’m all for looking on the bright side but this is a bit much lol
Linux users online tend to get very high and mighty every time another OS has a sucurity bug. But it’s a good thing for Linux hehe
That’s because illuminating security vulnerabilities is VERY GENERALLY a good thing for an open source community driven software that can be more agile than closed and private code bases that are GENERALLY entrenched in a corporate structure slowed by all of the inertia inherent in those systems.
Don’t like all Linux patches have to be emailed directly to chappy for him to personally check?
wtf does this mean?
No, that’s just for development discussion and code versioning. Nothing the end-user needs to touch or see.
End users update their system with commands/through interfaces or they receive automatic updates, depending on their system.
We’re talking about patching the kernel though.