From owner-freebsd-questions  Sun Nov 18  4:45: 5 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 5ECC437B416; Sun, 18 Nov 2001 04:45:02 -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 fAICitK17301; Sun, 18 Nov 2001 13:44:55 +0100 (CET)
Message-ID: <03af01c1702e$d38c0520$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "Andrew C. Hornback" <achornback@worldnet.att.net>,
	"Greg Lehey" <grog@FreeBSD.ORG>,
	"FreeBSD Questions" <freebsd-questions@FreeBSD.ORG>
References: <002701c16fda$ca673680$6600000a@ach.domain>
Subject: Re: Mysterious boot during the night
Date: Sun, 18 Nov 2001 13:44:49 +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: <freebsd-questions.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-questions>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-questions>
X-Loop: FreeBSD.ORG

Andrew writes:

> Just to be safe, I'd still seek some kind of
> diagnostic just to make sure.

That would not be logical.  Hardware failures are extremely rare; software
failures are extremely common.  It doesn't make sense to spend time trying to
rule out hardware (which is never actually possible, anyway) when a software
error is more likely to be the culprit.

> I'm not 100% sure about this, but I believe that
> if you CVSupped to the newest version, it might
> include the fix.

I have something that I got somewhere with cvsup; maybe it was source, or the
latest ports, or something.  I don't know exactly what source is currently on
the machine.

In general, I do not update an entire operating system in a shotgun approach to
fixing a problem of unknown origin, as it often causes more problems than it
solves.

> Your best bet, I believe, is going to be to talk
> with sos and see about getting the patch either
> MFC'd to the STABLE branch, or to get a copy of the
> patch yourself and apply it.

Who is sos?

How do I know that this patch will fix the problem?


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message