On Mon, Oct 20, 2003 at 02:36:00PM -0500, Brian Elliott Finley wrote: > > Are there any major distros that don't include a .config file with their > kernel(s)? I know that SuSE provides a /proc/config.gz, which is > _really_ nice, that we could always check for first as it will always > match the running kernel.
Debian & RedHat install a /boot/config-<vers>. however, people who build their own kernels will need to point us to theirs. > > This is a difficult question. > > Brain storming: dmesg freshly booted machine will tell us the order that > certain drivers were loaded, but not necessarily info for all devices. > I think some drivers may load silently. quite often the ring buffer will be overwritten or a user is running a daemon that periodically clears this. floating-point assist faults make this very likely on ia64. > However! It seems that I've never met a network or disk driver that > didn't record some info into the ring buffer. Maybe we can use that in > some way? the inconsistencies make this difficult - we'd need some special code to deal with the parsing of the messages for each driver. > > Once we have the list of modules, we can determine which ones reside > > in drivers/net, and make sure those are loaded in the initrd. It'd > > probably also be a good idea to copy over modules.conf, so we get > > any weird options that may need to be passed. > > Some systems now use /etc/modules also, or instead of modules.conf. > We may need to take that into consideration too. yeah. ------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 _______________________________________________ Sisuite-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
