From owner-freebsd-small@FreeBSD.ORG  Thu Sep 15 23:27:12 2005
Return-Path: <owner-freebsd-small@FreeBSD.ORG>
X-Original-To: freebsd-small@freebsd.org
Delivered-To: freebsd-small@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CD1EB16A42C
	for <freebsd-small@freebsd.org>; Thu, 15 Sep 2005 23:27:12 +0000 (GMT)
	(envelope-from snoel@gestosoft.com)
Received: from tomts5-srv.bellnexxia.net (tomts5.bellnexxia.net
	[209.226.175.25])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F347A43D46
	for <freebsd-small@freebsd.org>; Thu, 15 Sep 2005 23:27:11 +0000 (GMT)
	(envelope-from snoel@gestosoft.com)
Received: from [10.0.5.53] ([69.156.84.58]) by tomts5-srv.bellnexxia.net
	(InterMail vM.5.01.06.10 201-253-122-130-110-20040306) with ESMTP
	id <20050915232710.CNZD26967.tomts5-srv.bellnexxia.net@[10.0.5.53]>;
	Thu, 15 Sep 2005 19:27:10 -0400
In-Reply-To: <m23bofvvm1.wl%gnn@neville-neil.com>
References: <W903802119519351126194088@webmail2>
	<20050908165951.GE31354@odin.ac.hmc.edu>
	<m2vf1bwj69.wl%gnn@neville-neil.com>
	<E42CAEEC-0382-44D3-8A9D-38E1B3AE7B4E@gestosoft.com>
	<m23bofvvm1.wl%gnn@neville-neil.com>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F0169D41-0450-4973-9FF4-A9D743DA904C@gestosoft.com>
Content-Transfer-Encoding: 7bit
From: Sandro Noel <snoel@gestosoft.com>
Date: Thu, 15 Sep 2005 19:27:09 -0400
To: gnn@neville-neil.com
X-Mailer: Apple Mail (2.734)
Cc: freebsd-small@freebsd.org
Subject: Re: System Tree essentials UNDERSTANDING the system
X-BeenThere: freebsd-small@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Dedicated and Embedded Systems <freebsd-small.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-small>,
	<mailto:freebsd-small-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-small>
List-Post: <mailto:freebsd-small@freebsd.org>
List-Help: <mailto:freebsd-small-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-small>,
	<mailto:freebsd-small-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Sep 2005 23:27:12 -0000

George.

Ok i've been looking at the kernel files. for a way to map the kernel  
globals / options / devices / hints
for all the ARCH's including dependencies on other options
same for devices and their dependencies, and hints.

for instance
rl, re, depend on miibus
and miibus depends on pci.
some devices have hints attached to them, (easy to find because or  
the names)

then after that is mapped i was planing on checking the modules for  
dependencies to
these options/devices
and map them in the same manner.

for instance if you want to have a sound blaster live sound device
you need the emu10k module, and that module needs the sound option to  
be in the kernel config file.
i think....

dependencies would have to be mapped by hand.
in a file or database that we can update

The goal is to produce a configuration file for config to process.
and probably a loader.conf file

now what i want to know from you is, am i about to do this for  
nothing because there is already
something out there doing the same thing? or some trick i am not  
aware about that already does
most of the work.

If not, what would be the best practice to store this information to  
ease up editing, updating and use,
according to your experience.

Sandro.