Simply by default of the high-security risk lately of Windows systems, daily security patches, mandatory hard power recycling style reboots of OS and lacking auto-patching Windows has certainly lost its edge.
In part, if people have to manage, watch and reboot so much, the additional investments to move to a Linux environment are seemingly negligible... This coupled with a ready stream of young and energetic current college graduates who have exposure to Linux, will lead more businesses to move their server environment to Linux platform. That's my opinion and boy have I been a MS server head for years... Also, the rollup packages and patching mechanisms suck... Just to install a fresh box involved around 5 reboots, since a lot of MS crappy patches require exclusive patch operation followed by a reboot. My .02 cents. -paris -----Original Message----- From: Dalrymple, B Keith [mailto:[EMAIL PROTECTED]] Sent: Monday, February 25, 2002 15:31 To: CF-Server Subject: RE: PC Server Stability Sure, you leave yours set up with the original 65234 security problems and lets see how long it takes for a hacker to get serious. You r call is not mine! -----Original Message----- From: Dave Watts [mailto:[EMAIL PROTECTED]] Sent: Monday, February 25, 2002 12:27 PM To: CF-Server Subject: RE: PC Server Stability > I have MS 2000 servers that due to upgrades every week > are being rebooted @ least once per week. I have a Linux > system that is only rebooted when upgrades are added > and this is a lot less frequently than Windows systems. If it helps, you don't have to constantly patch your Windows servers. Just set them up correctly in the first place, and most of the patches will be irrelevant. Remove unused ISAPI extensions, and so on. You should only rarely have to patch a production server, and in most cases, this can be done on a scheduled basis. I've got some Windows servers which have been running nonstop for years - they only get shutdown when they're moved to a different physical location! > Windows systems stay up longer if they are running > automated Defragmentation S/W. If the filesystem is organized well, this isn't usually necessary. Typically, on running production servers, the filesystem contents shouldn't change all that frequently. However, the fact that you raise both these points is useful and valid, in that it illustrates one of the "hidden" costs of Windows administration - anyone can set up a Windows box, but to administer it well, you have to know what you're doing, just like with Unix. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com ------------------------------------------------------------------------------ To unsubscribe, send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body or visit the list page at www.houseoffusion.com
