From owner-freebsd-questions  Sun Nov 18 12:26:59 2001
Delivered-To: freebsd-questions@freebsd.org
Received: from mtiwmhc26.worldnet.att.net (mtiwmhc26.worldnet.att.net [204.127.131.51])
	by hub.freebsd.org (Postfix) with ESMTP
	id D33BB37B417; Sun, 18 Nov 2001 12:26:47 -0800 (PST)
Received: from columbia ([12.93.210.159]) by mtiwmhc26.worldnet.att.net
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with SMTP
          id <20011118202646.RBXG4964.mtiwmhc26.worldnet.att.net@columbia>;
          Sun, 18 Nov 2001 20:26:46 +0000
From: "Andrew C. Hornback" <achornback@worldnet.att.net>
To: "Anthony Atkielski" <anthony@atkielski.com>,
	"Greg Lehey" <grog@FreeBSD.ORG>,
	"FreeBSD Questions" <freebsd-questions@FreeBSD.ORG>
Subject: RE: Mysterious boot during the night
Date: Sun, 18 Nov 2001 15:26:44 -0500
Message-ID: <005201c1706f$572afb80$6600000a@ach.domain>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
In-Reply-To: <03af01c1702e$d38c0520$0a00000a@atkielski.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
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

> -----Original Message-----
> From: Anthony Atkielski [mailto:anthony@atkielski.com]
> Sent: Sunday, November 18, 2001 7:45 AM
> To: Andrew C. Hornback; Greg Lehey; FreeBSD Questions
> Subject: Re: Mysterious boot during the night
>
> 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.

	It's not logical to create a baseline of your system by testing it's
components?  Hmm... guess I've not been following "logical" practices for
years now, and don't think I'm going to stop.

> > 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.

	You don't need to update the entire operating system if you can procure and
install the patch.

> > 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?

	I don't know personally, but from what Greg has mentioned in previous
posts, I imagine sos is the person that wrote the patch to make the FreeBSD
work properly with the IDE Controller chipset on your motherboard.

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

	You may have to ask... but, from what Greg has said, the patch was written
specifically to make your chipset compatable with FreeBSD.

--- Andy


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