On 06/01/12 05:16, lina wrote: <snipped> > > Are there some intelligent package, something like read the lspci > and other hardware information. And according the info to vim the > .config
NAFAIK (yet...) though I keep looking and I've started on something similar a few times based on Knoppix and using kudzu. It's on that long list of things to do if I live that long ;-) Your best bet is probably to set up a stock system that supports all your hardware and also your networking needs. Choose the light, targeted (rather than generic), initrd. Decide whether you intend to build kernel that uses initrd or not (load all modules or have them built in) - then examine loaded modules to see what you need, and remove unneeded built-in kernels. Pretty much the technique used for building kernels for embedded systems. The automated part you're looking for - there are a couple of scripts around that attempt to do this for you, here's one[*1]:- http://andreas.goelzer.de/kernel-config-based-on-lsmod-output > I don't have much hardware knowledge either, so can't build a > specific and light kernel. Last one I build the /lib/module so > heavy. You don't really need the hardware knowledge - just to know what you have that you want supported. <snipped> Cheers -- Iceweasel/Firefox extensions for finding answers to Debian questions:- https://addons.mozilla.org/en-US/firefox/collections/Scott_Ferguson/debian/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f0650fb.6090...@gmail.com
