From owner-freebsd-hackers  Thu Jun  8 22:21:58 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id WAA13544
          for hackers-outgoing; Thu, 8 Jun 1995 22:21:58 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA13533
          for <freebsd-hackers@freebsd.org>; Thu, 8 Jun 1995 22:21:53 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA18583; Fri, 9 Jun 1995 15:17:32 +1000
Date: Fri, 9 Jun 1995 15:17:32 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199506090517.PAA18583@godzilla.zeta.org.au>
To: freebsd-hackers@freebsd.org, jbryant@argus.iadfw.net
Subject: Re: options "ALLOW_CONFLICT_IOADDR" don't work! (fwd)
Sender: hackers-owner@freebsd.org
Precedence: bulk

>> >options "ALLOW_CONFLICT_IOADDR" does not work!@#
>> ...
>> I really hate to say this, by RTFM!!!!!

>What FM?!@#

>> It is documented in LINT the correct solution to this problem -

LINT is self-documenting.

>> ALLOW_CONFLICT_IOADDR was a HACK of the gross order, and there is now
>> another field in the device declaration line which allows
>> conflicts. See LINT for more.

`conflicts' seems to be missing from userconfig().

Bruce