From owner-cvs-usrsbin  Wed May 10 19:22:10 1995
Return-Path: cvs-usrsbin-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id TAA13136
          for cvs-usrsbin-outgoing; Wed, 10 May 1995 19:22:10 -0700
Received: from time.cdrom.com (time.cdrom.com [192.216.223.46])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA13118
          ; Wed, 10 May 1995 19:21:51 -0700
Received: (from jkh@localhost) by time.cdrom.com (8.6.11/8.6.9) id TAA07545; Wed, 10 May 1995 19:21:38 -0700
Date: Wed, 10 May 1995 19:21:38 -0700
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Message-Id: <199505110221.TAA07545@time.cdrom.com>
To: CVS-commiters@time.cdrom.com, cvs-usrsbin@time.cdrom.com
Subject: cvs commit: src/usr.sbin/config config.h config.y lang.l mkioconf.c
Sender: cvs-usrsbin-owner@freebsd.org
Precedence: bulk

jkh         95/05/10 19:21:37

  Modified:    usr.sbin/config  config.h config.y lang.l mkioconf.c
  Log:
  Add a new `conflicts' flag for telling when a device is in conflict with
  others.  The flag can be put in descriptive locations, e.g.:
  
  device sb0      at isa? port 0x220 irq 7 conflicts drq 1 vector sbintr
  or
  device psm0	at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr
  
  But is nonetheless boolean only.  You can't turn conflict checking off for
  only a given type of conflict.  I didn't deem it worth the trouble at this
  stage, and it's far better than the ALLOW_CONFLICT_* that preceeded it.