2226
General Software Discussion / Re: Stop Windows from calling home
« on: January 04, 2010, 08:55 PM »You're the one who flat-out claimed that packet filters aren't firewallsPacket filters and "real" (hardware) firewalls work on the network layer, "software firewalls" mainly on the application layer. (With a driver-thingy on another layer, probably, but then we'll have a packet filter again.)-f0dder (January 04, 2010, 08:02 PM)
and that Windows' built-in firewall is useless... and potentially dangerous.-f0dder (January 04, 2010, 08:02 PM)
2) why would't I run an important server on a Windows box?Because Windows is not known for stability and security, both of them are the most important attributes of servers IMO.-f0dder (January 04, 2010, 08:02 PM)
(Oh, and Windows' cmd.exe without [at least] some *ix tools is, at best, a sick joke when it is about configuration and server maintenance. This refers explicitly to this special case. In other threads I'll stick with my opinion that cmd.exe is everything I need. Maybe because I don't have to control a server system with it. But we're drifting a bit OT here, aren't we?)
Ever checked this list?Uptime depends on various things. That Windows servers are on top of the list doesn't necessarily mean something. (edit: Missed a dot.)-f0dder (January 04, 2010, 08:02 PM)
My personal fileserver (which can hardly be thought of as a critical machine) runs linux - simply because it's free. Free as in beer.Now that's not actually a reason. If it was, no-one would use Windows anymore, as it is not free. :D-f0dder (January 04, 2010, 08:02 PM)