Date: Thu, 15 Sep 2005 19:27:09 -0400 From: Sandro Noel <snoel@gestosoft.com> To: gnn@neville-neil.com Cc: freebsd-small@freebsd.org Subject: Re: System Tree essentials UNDERSTANDING the system Message-ID: <F0169D41-0450-4973-9FF4-A9D743DA904C@gestosoft.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F0169D41-0450-4973-9FF4-A9D743DA904C>