From owner-freebsd-current  Fri Oct 27  9:34:18 2000
Delivered-To: freebsd-current@freebsd.org
Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229])
	by hub.freebsd.org (Postfix) with ESMTP
	id 033A337B479; Fri, 27 Oct 2000 09:34:17 -0700 (PDT)
Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1])
	by winston.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id e9RGY7455564;
	Fri, 27 Oct 2000 09:34:07 -0700 (PDT)
	(envelope-from jkh@winston.osd.bsdi.com)
To: obrien@FreeBSD.ORG
Cc: current@FreeBSD.ORG
Subject: Re: AMD broken in -current? 
In-Reply-To: Message from "David O'Brien" <obrien@FreeBSD.ORG> 
   of "Thu, 26 Oct 2000 21:52:35 PDT." <20001026215234.C9231@dragon.nuxi.com> 
Date: Fri, 27 Oct 2000 09:34:07 -0700
Message-ID: <55560.972664447@winston.osd.bsdi.com>
From: Jordan Hubbard <jkh@winston.osd.bsdi.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> On Thu, Oct 26, 2000 at 09:04:45PM -0700, Jordan Hubbard wrote:
> > It use to work in early October, but now I get the following using
> > the stock (/etc/defaults/rc.conf) amd flags:
> 
> It works on my Oct 22nd world.

OK, so maybe it broke even later.  What does it do on your
Oct 27th world? :)

- Jordan


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