From owner-freebsd-current  Tue Oct  1 01:18:51 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id BAA05829
          for current-outgoing; Tue, 1 Oct 1996 01:18:51 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA05822;
          Tue, 1 Oct 1996 01:18:48 -0700 (PDT)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id BAA29203; Tue, 1 Oct 1996 01:18:48 -0700 (PDT)
To: bde@freebsd.org
cc: current@freebsd.org
Subject: Your UserConfig changes for unmasking PCI devices...
Date: Tue, 01 Oct 1996 01:18:48 -0700
Message-ID: <29201.844157928@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Will have to be either disabled or revamped before I do my next
snapshot, I'm afraid.  As it stand now, even a non-PCI machine will
have a bewildering number of duplicate entries with no apparent rhyme
or reason to them and users are going to be _confused_.

The drivers listed twice in the current GENERIC kernel are:
	bt0
	ed0
	lnc0

And deleting any of the PCI entries, BTW, is now grounds for an
immediate panic once you continue.  Whups.

In any case, I was kind of hoping to do an October snapshot soon -
what are your plans for userconfig?

					Jordan