From owner-freebsd-current  Tue Oct  1 02:58:25 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id CAA10621
          for current-outgoing; Tue, 1 Oct 1996 02:58:25 -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 CAA10615;
          Tue, 1 Oct 1996 02:58:20 -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 CAA11845; Tue, 1 Oct 1996 02:58:15 -0700 (PDT)
To: Michael Smith <msmith@atrad.adelaide.edu.au>
cc: bde@freebsd.org, current@freebsd.org
Subject: Re: Your UserConfig changes for unmasking PCI devices... 
In-reply-to: Your message of "Tue, 01 Oct 1996 19:09:10 +0930."
             <199610010939.TAA11012@genesis.atrad.adelaide.edu.au> 
Date: Tue, 01 Oct 1996 02:58:15 -0700
Message-ID: <11843.844163895@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>  - "different text attributes" aren't (properly) supported by syscons
>    at that point in the boot process.

Ah.  Phoo.

>  - how is userconfig supposed to know what hardware the system has?  I
>    thought the whole idea behind it was for it to run _before_ hardware
>    had been located, not afterwards.

Erm.  Ya got me there, pardner! :-)

> I only planned to put PCI devices in as a calmative for users who 
> might otherwise bitch about not being able to see them.  It might make
> more sense just to rip them right out again.

I'm leaning that way myself unless we can figure out a way of doing
a better job.  How about a one-line summary somewhere like this:

	PCI device support for:  bt0 ed0 lnc0

On the screen? :-)
					Jordan