From owner-freebsd-hackers  Sun Oct 12 14:22:17 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id OAA17072
          for hackers-outgoing; Sun, 12 Oct 1997 14:22:17 -0700 (PDT)
          (envelope-from owner-freebsd-hackers)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA17064
          for <hackers@FreeBSD.ORG>; Sun, 12 Oct 1997 14:22:14 -0700 (PDT)
          (envelope-from jkh@time.cdrom.com)
Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id OAA05019; Sun, 12 Oct 1997 14:21:18 -0700 (PDT)
To: Terry Lambert <tlambert@primenet.com>
cc: hoek@hwcn.org, hackers@FreeBSD.ORG
Subject: Re: fnord0: disabled, not probed. 
In-reply-to: Your message of "Sun, 12 Oct 1997 21:13:21 -0000."
             <199710122113.OAA21916@usr05.primenet.com> 
Date: Sun, 12 Oct 1997 14:21:18 -0700
Message-ID: <5015.876691278@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Fie.  There is a technological soloution to this problem, and a kludge
> should not be used.  The messages are a warning that a correct fix has
> yet to be implemented.  Removing them removes pressure to fix the thing
> the correct way, and encourages a climate of kludges.

Naw.  The correct way to fix them involves the load-reject-and-unload
dynamic driver interface you're so fond of.  Then this message goes
away anyhow since there's no such thing as a "disabled" driver in that
context and you've really saved yourself nothing by keeping it.  All
it's reminding us of is the fact that we need to substantially
rearchitect our device driver subsystem and we get plenty of reminders
of that from other sources already. :-)

					Jordan