From owner-freebsd-hackers Sun Oct 12 17:05:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA29908 for hackers-outgoing; Sun, 12 Oct 1997 17:05:56 -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 RAA29903 for ; Sun, 12 Oct 1997 17:05:53 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id RAA02085; Sun, 12 Oct 1997 17:05:43 -0700 (MST) From: Terry Lambert Message-Id: <199710130005.RAA02085@usr05.primenet.com> Subject: Re: fnord0: disabled, not probed. To: ac199@hwcn.org Date: Mon, 13 Oct 1997 00:05:43 +0000 (GMT) Cc: tlambert@primenet.com, hoek@hwcn.org, jkh@time.cdrom.com, hackers@FreeBSD.ORG In-Reply-To: from "Tim Vanderhoek" at Oct 12, 97 05:32:23 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > There's always scroll-lock and dmesg (heh: "Are there no work houses, > > are there no prisons?"). > > You check dmesg for each and every time you boot your computer? > Indeed, you are a better man than I! No, I check it if I have unexplained problems. Besides, I learned to read the significant stuff scrolling at 19.2 a long time ago... 8-). > Besides, only a schmuck would take action A, which has an unknown > result, and assume that reaction C is unrelated. :) (Where A is > disabling devices he doesn't recognize and C is a missing hdd :). I'd agree, except for "device npx0 ..." shoots a whole in your thesis. It claims to be optional (by having a line in the configuration file, it is implied that it need not be configured in a minimal kernel). If the entire source tree were internally consistent, then you'd have a case. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.