From owner-freebsd-questions Sun Nov 18 18: 7:19 2001 Delivered-To: freebsd-questions@freebsd.org Received: from atkielski.com (atkielski.com [161.58.232.69]) by hub.freebsd.org (Postfix) with ESMTP id 98FEC37B405; Sun, 18 Nov 2001 18:07:16 -0800 (PST) Received: from contactdish (ASt-Lambert-101-2-1-14.abo.wanadoo.fr [193.251.59.14]) by atkielski.com (8.11.6) id fAJ27DF98914; Mon, 19 Nov 2001 03:07:13 +0100 (CET) Message-ID: <003a01c1709e$e8318e30$0a00000a@atkielski.com> From: "Anthony Atkielski" To: "Andrew C. Hornback" , "Greg Lehey" , "FreeBSD Questions" References: <005201c1706f$572afb80$6600000a@ach.domain> Subject: Re: Mysterious boot during the night Date: Mon, 19 Nov 2001 03:07:07 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Andrew writes: > It's not logical to create a baseline of your > system by testing it's components? It's not logical to test components that are extremely unlikely to be malfunctioning. At one time, when PCs were a laboratory curiosity and only worked correctly on occasion, testing the hardware might have made more sense (although, overall, PC hardware has always been remarkably reliable). Today, however, there is no reason at all to test hardware unless clear evidence of hardware failure becomes apparent. Software, on the other hand, has never been reliable, and has not become any more reliable over time. It therefore makes sense to be extremely wary of software, and to test software configurations frequently. > Hmm... guess I've not been following "logical" > practices for years now, and don't think I'm going > to stop. It's up to you, but time spent running lots of hardware tests could probably be better spent in other ways these days. > You don't need to update the entire operating > system if you can procure and install the patch. Good. So how do I know that this patch is related to the mysterious boot I observed? > You may have to ask... but, from what Greg has > said, the patch was written specifically to make > your chipset compatable with FreeBSD. Fine, but how do I know that a chipset incompatibility had anything to do with my problem? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message