daedaliavallis: Except it does, and it's not a myth. It's happened to me, repeatedly, on my laptop while I was working with no prompting to reboot, and kept doing it after every update until I finally found a way to disable the Borg-like regenerative update permanently.

Kelefane: It's never happened to me and people I know.

djoxyk: right, and the Earth is flat because you can clearly see it with your own eyes

daedaliavallis: Except it does, and it's not a myth. It's happened to me, repeatedly, on my laptop while I was working with no prompting to reboot, and kept doing it after every update until I finally found a way to disable the Borg-like regenerative update permanently.

Cavalary: -words-

Darvond: My TL;DR to you is that I've never even really bothered with trying to make rules or white lists because I prefer to keep my aluminum sheets for pizzas.

Cavalary: So again, nothing to discuss regarding suitability of Linux for my uses, just a resounding no. And condescending too.
The tl;dr is that I want to be able to fully control and monitor my system, and the connections made from my system in particular, and won't use an OS where I won't be able to easily do that.

Darvond: You can do that; via gui or command line tools, but I wouldn't the one to ask how. Linux is popular for servers for a reason.

JackBurton.: Im always using each version of windows till the end

djoxyk: right, and the Earth is flat because you can clearly see it with your own eyes

Ancient-Red-Dragon: ...MS has always made their OSes become obsolete over time to the point that they all eventually become totally unusable.

Cavalary: I mean something very much like Comodo Firewall is for Windows. Can create both global and application rules, whenever something tries a connection that doesn't match a rule I get a prompt, can say from the prompt whether the answer applies just for that connection or a rule is to be created, have customizable rule types which I can use to set rule parameters in 2 clicks either from the prompt or manually, can further customize each rule in detail manually if I care to, decide what gets logged, see at any moment each connection, with process, destination, source, protocol, port and traffic made in and out, also allows to block sites/IPs...
And major bonus, has HIPS too, in the firewall that is, without also installing the antivirus, so you can pair it with a proper antimalware solution (since CAV isn't that highly rated), which is quite a Swiss army knife for that as well for anyone who cares and knows how to use it. I tend to largely use it to learn what programs try to do, set it to auto-allow signed or trusted programs but then check the rules it creates just for curiosity. And when I do get prompts for non system stuff I tend to try to block and see what happens. One thing I do block in general is for example allowing games to check network settings, since I don't want them to connect, so I block some from even trying even before getting to firewall, or block some that try inter-process memory access for some reason. Didn't have them crash so far due to those things, so keep wondering why they'd try.
But yeah, that's largely curiosity, though a proper HIPS mostly makes another antimalware solution quite useless. But a proper firewall like that is something I will not use a computer without.

Cavalary: Actually quite fond of command line stuff, there are things (on Windows, I mean) that I still prefer to do via command line even if there's a built-in GUI. But command line tools are completely unsuited for a firewall, the way I use one at least.