From owner-freebsd-current  Wed May 10 22:07:45 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id WAA17171
          for current-outgoing; Wed, 10 May 1995 22:07:45 -0700
Received: from who.cdrom.com (who.cdrom.com [192.216.222.3])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA17162
          ; Wed, 10 May 1995 22:07:43 -0700
Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12])
          by who.cdrom.com (8.6.11/8.6.11) with ESMTP id WAA00639
          ; Wed, 10 May 1995 22:01:03 -0700
Received: (from nate@localhost) by trout.sri.MT.net (8.6.11/8.6.11) id XAA23725; Wed, 10 May 1995 23:08:05 -0600
Date: Wed, 10 May 1995 23:08:05 -0600
From: Nate Williams <nate@trout.sri.MT.net>
Message-Id: <199505110508.XAA23725@trout.sri.MT.net>
To: "Jordan K. Hubbard" <jkh@freefall.cdrom.com>
Cc: current@freefall.cdrom.com
Subject: Re: new config update.
In-Reply-To: <13379.800159313@freefall.cdrom.com>
References: <13379.800159313@freefall.cdrom.com>
Sender: current-owner@FreeBSD.org
Precedence: bulk

Jordan K. Hubbard writes:
> The config program has been updated to incorporate a new `conflicts'
> keyword.  This replaces the ALLOW_CONFLICT_* bodge I first stuck in
> there and is now, at least, device specific rather than kernel-wide.
> It could all still be much improved, but is nonetheless an improvement
> over what we had before.

I'm in agreement that it's a botch, but since the reason that it exists
in the first place is a botch anyway, it's not too bad of solution.

Thanks!


Nate