From owner-freebsd-current  Sun Nov 29 15:13:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA13792
          for freebsd-current-outgoing; Sun, 29 Nov 1998 15:13:16 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13786
          for <freebsd-current@FreeBSD.ORG>; Sun, 29 Nov 1998 15:13:15 -0800 (PST)
          (envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1])
	by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id PAA20483;
	Sun, 29 Nov 1998 15:14:22 -0800 (PST)
To: "Richard B. Ernst" <ernst@wizard.com>
cc: Stephen McKay <syssgm@dtir.qld.gov.au>, freebsd-current@FreeBSD.ORG
Subject: Re: 2.2.7-->current shortcut *boom* 
In-reply-to: Your message of "Sun, 29 Nov 1998 15:08:30 PST."
             <Pine.BSF.4.02.9811291505530.14248-100000@snark.wizard.com> 
Date: Sun, 29 Nov 1998 15:14:22 -0800
Message-ID: <20475.912381262@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Still no joy on getting -current (from CVS) to compile on a very mixed up
> system.   More suggestions?

Maybe unmix the system by doing a fresh installation before attempting
any further to untangle this knot from the inside? :)

- Jordan

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