From owner-freebsd-hackers  Sat Apr 29 05:08:59 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id FAA23828
          for hackers-outgoing; Sat, 29 Apr 1995 05:08:59 -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 FAA23809
          for <hackers@FreeBSD.org>; Sat, 29 Apr 1995 05:08:19 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id WAA22510; Sat, 29 Apr 1995 22:05:43 +1000
Date: Sat, 29 Apr 1995 22:05:43 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199504291205.WAA22510@godzilla.zeta.org.au>
To: dufault@hda.com, jkh@time.cdrom.com
Subject: Re: Boot message rampage
Cc: hackers@FreeBSD.org
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

>> All the probe messages irritate the hell out of me.  The style is

>Boy do I agree with this.  I have two 8 port serial cards in one of my
>kernels.

Do you have the verbose com flag enabled or drivers for nonexistent
multiport serial cards?  Normally only 2 lines of output per port are
printed, but you can get about 10 lines per port in some
misconfigurations :-).

>I agree.  I propose we do provide something similar to the "write out the
>config" so that you can zap your kernel to support the boot flags you
>want.

I have a utility for this (written by Christoph Robitschko) but haven't
found it very useful.  Zapping the flags at boot time is more convenient.
(Today I found a limitation in userconfig().  After zapping some interrupts
from -1 to active, the interrupt handlers remained as 0 and caused a
panic.  userconfig() neither displays nor allows zapping the interrupt
handlers.)

Bruce