Date: Thu, 13 Apr 2006 04:17:24 -0700 From: MC <rossiya@gmail.com> To: freebsd-stable@freebsd.org Subject: Re: Disappointed Message-ID: <28a99ba50604130417x613170d3x9343d2286b03fbb6@mail.gmail.com> In-Reply-To: <20060413135730.557ab663@localhost> References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <c7aff4ef0604060458u1a019e0dna740f61e53299c25@mail.gmail.com> <b84edfa10604060612s21e4ebb9w1d3465f1418cb242@mail.gmail.com> <b84edfa10604060613w36b02f3dhcda5d4fb6c3a393f@mail.gmail.com> <c7aff4ef0604060623g575bf32fh890d3471c978759b@mail.gmail.com> <20060410215633.GA2483@soaustin.net> <20060413135730.557ab663@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
I have installed freeBSD more than 1000 times, on hundreds of machines. Some of them had no business being called a computer outright, as their reliability was more constrained by chaotic feedback than Von Newman architecture. Memory would disappear while running, DRAM would fail, 3com NICS would drop their checksums, voltages would drop, fans would stop cooling, admins would pull the mains. Somewhere around 2000 FreeBSD became more stable than the hardware it ran upon, given halfway decent administration. By tha= t I mean installing releases and keeping track of release notes. There have been some longstanding bugs that took years to iron out, but I never reported them or patched them myself, implying ultimately the problem wasn't mission critical. Of course some will install CURRENT with GCC O6 and then complain about a kernel panic
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?28a99ba50604130417x613170d3x9343d2286b03fbb6>