Return to BSD News archive
Xref: sserve comp.os.linux.networking:10781 comp.os.ms-windows.networking.tcp-ip:13279 comp.unix.bsd.freebsd.misc:4000 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.duke.edu!solaris.cc.vt.edu!swiss.ans.net!prodigy.com!davidsen From: davidsen@tmr.com (bill davidsen) 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 15:51:24 GMT Organization: TMR Associates, Schenectady NY Lines: 14 Message-ID: <3v5o9s$ug6@usenetw1.news.prodigy.com> References: <3ue5qa$ain@panix.com> <DC3sEM.1Jr@saturn.tlug.org> <tgmDC46x0.A4M@netcom.com> <3v4l78$ltr@enigma.uniserve.com> NNTP-Posting-Host: 199.4.137.118 Originator: davidsen@darkstar.prodigy.com In article <3v4l78$ltr@enigma.uniserve.com>, Tom Samplonius <tom@uniserve.com> wrote: | 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). Stop posting facts, it confuses zealots...