From owner-freebsd-current Wed Oct 9 15:31:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA13448 for current-outgoing; Wed, 9 Oct 1996 15:31:18 -0700 (PDT) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA13436 for ; Wed, 9 Oct 1996 15:31:13 -0700 (PDT) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.7.6/8.7.3) with SMTP id RAA04860; Wed, 9 Oct 1996 17:30:36 -0500 (EST) Date: Wed, 9 Oct 1996 17:30:35 -0500 (EST) From: John Fieber To: Charles Henrich cc: "Jordan K. Hubbard" , hoek@freenet.hamilton.on.ca, freebsd-current@FreeBSD.org Subject: Re: 961006-SNAP comments In-Reply-To: <199610091306.JAA05163@crh.cl.msu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 9 Oct 1996, Charles Henrich wrote: > Why are we forcing people who probably have no clue to go mucking with the > device table? Because this marvelous PC architecture we have often requires it. Except for people who use only the hardware and software that came installed on there machine, just about every PC user will at some point confront IRQs and the like, or they will pay someone else to. If we try and hide the issue, a fair number of people will reach a dead end and give up before they get started. This snapshot represent a first approach at confronting the issue directly. I'll agree that it needs to be refined, but considering we can't change the PC architecture, its the best direction to go. Don't be so anxious to throw out the idea just because its new and doesn't solve a problem you have. -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================