Return to BSD News archive
Xref: sserve comp.os.linux.networking:10754 comp.os.ms-windows.networking.tcp-ip:13257 comp.unix.bsd.freebsd.misc:3976 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!noc.netcom.net!ix.netcom.com!howland.reston.ans.net!math.ohio-state.edu!news.cyberstore.ca!vanbc.wimsey.com!fonorola!uniserve1!usenet From: tom@uniserve.com (Tom Samplonius) Newsgroups: comp.os.linux.networking,comp.os.ms-windows.networking.tcp-ip,comp.unix.bsd.freebsd.misc Subject: Re: Internet service providing-which OS? Date: 26 Jul 1995 05:52:40 GMT Organization: UNIServe Online Lines: 13 Message-ID: <3v4l78$ltr@enigma.uniserve.com> References: <3ue5qa$ain@panix.com> <id.VAPL1.0SA@nmti.com> <3ugeup$44k@news.unicomp.net> <3uk3b5$35a@legend.txdirect.net> <DC3sEM.1Jr@saturn.tlug.org> <tgmDC46x0.A4M@netcom.com> NNTP-Posting-Host: pc.sdf.com Mime-Version: 1.0 X-Newsreader: WinVN 0.99.2 In article <tgmDC46x0.A4M@netcom.com>, tgm@netcom.com says... >Without a doubt, the crash of '95 was ftp.cdrom.com and FreeBSD. What >was the cost to the Internet community? What would be the cost to your >business to lose connectivity for a week? How "Free" is FreeBSD when >you factor in over a week of downtime? Face it, if you need 24 hour per >day, 365 day per year reliability, FreeBSD will *NOT* cut it. Wait a second, the crash was a HARDWARE failure (SCSI controller and several drives). Tom