From owner-freebsd-current Thu Apr 6 00:43:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA14288 for current-outgoing; Thu, 6 Apr 1995 00:43:36 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA14279 ; Thu, 6 Apr 1995 00:43:34 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id AAA11947; Thu, 6 Apr 1995 00:43:34 -0700 From: Poul-Henning Kamp Message-Id: <199504060743.AAA11947@ref.tfs.com> Subject: Re: Strange kernel printf... To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Thu, 6 Apr 1995 00:43:33 -0700 (PDT) Cc: bde@zeta.org.au, ache@astral.msk.su, rgrimes@gndrsh.aac.dev.com, freebsd-current@freefall.cdrom.com In-Reply-To: <9774.797139762@freefall.cdrom.com> from "Jordan K. Hubbard" at Apr 5, 95 08:42:42 pm Content-Type: text Content-Length: 678 Sender: current-owner@FreeBSD.org Precedence: bulk > 1. Generate arrays of allocated addresses, IRQs (are there any devices > made that more than one?), DMA channels, etc. where it currently holds > only a single value. nca0 for the PAS16, and the sound-drivers come to mind... > Seriously, we always talk about how evil config is but no one really > does anything about it. Sort of like our attitude towards government, > but I digress. How hard would it REALLY be to finally fix config > properly? as in "get rid of config entirely" ? -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant'