From owner-freebsd-current  Wed Dec 15  9:52:12 1999
Delivered-To: freebsd-current@freebsd.org
Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2])
	by hub.freebsd.org (Postfix) with SMTP id 8EB1215154
	for <current@FreeBSD.ORG>; Wed, 15 Dec 1999 09:52:10 -0800 (PST)
	(envelope-from dmmiller@cvzoom.net)
Received: (qmail 20398 invoked from network); 15 Dec 1999 17:52:09 -0000
Received: from lcb13.cvzoom.net (63.65.159.13)
  by ns.cvzoom.net with SMTP; 15 Dec 1999 17:52:09 -0000
Date: Wed, 15 Dec 1999 12:51:08 -0500 (EST)
From: Donn Miller <dmmiller@cvzoom.net>
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Cc: current@FreeBSD.ORG
Subject: Re: Kernel config utility
In-Reply-To: <199912151741.MAA08347@khavrinen.lcs.mit.edu>
Message-ID: <Pine.BSF.4.20.9912151247130.31674-100000@lcb13.cvzoom.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 15 Dec 1999, Garrett Wollman wrote:

> Icons are probably not the right user interface.  I'd suggest
> something like Windows's ``hardware manager'' (in the System control
> panel).

Some people were afraid that it would end up like the Windows
registry.  Well, even if it did, I'd argue that it still wouldn't be too
bad.  The Windows registry has so many classes and entries, and I think
the kernel config would be smaller with not as many classes.  You'd have
the device class, and options class.  Then, you'd break devices down into
scsi, ide, etc.  Or, we could break them down into network, disk
controllers, sound, that way.

- Donn



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message