From owner-freebsd-hackers Sun Oct 12 14:30:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA17749 for hackers-outgoing; Sun, 12 Oct 1997 14:30:53 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from usr05.primenet.com (tlambert@usr05.primenet.com [206.165.6.205]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA17739 for ; Sun, 12 Oct 1997 14:30:49 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id OAA22722; Sun, 12 Oct 1997 14:30:32 -0700 (MST) From: Terry Lambert Message-Id: <199710122130.OAA22722@usr05.primenet.com> Subject: Re: fnord0: disabled, not probed. To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sun, 12 Oct 1997 21:30:31 +0000 (GMT) Cc: tlambert@primenet.com, hoek@hwcn.org, hackers@FreeBSD.ORG In-Reply-To: <5015.876691278@time.cdrom.com> from "Jordan K. Hubbard" at Oct 12, 97 02:21:18 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > 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. :-) Yes, but the boot messsage source is apparently the only one that's annoying enough to actually motivate anyone to actually change code. Since we've finally located the holy grail of motivation in this case, shouldn't it be used as a tool, rather than buried where no one will ever find it again? Shades of Jimmy Hoffa... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.