On Wednesday 13 February 2008, Simon Turner wrote:
> Strange it took almost a day before I could see my post! Guess I was
> "moderated"...
>
> Hi Mick,
> Thanks for the reply. I've gone through about 4 kernel recompiles,
> each time wondering with question marks over my head, sure I had
> everything compiled in... I ended up adding pretty much anything
> that would be related to "PCI", "USB", "PCMCIA", "SCSI"... with the
> exception of the modules specific to some hardware I clearly dont
> have.
>
> I kept a copy of my .config each time, so, I will be able to study
> what I changed between the 3rd and 4th recompiles.
>
> I have to say, it was my first adventure playing around with the
> kernel, and I reached a high level of frustration, impatience but the
> level of my greed kept being at the top and I'd say it simply changed
> my life! =)
>
> I just find "make menuconfig" a bit confusing when searching for
> things... a simple grep on Kconfigs is so much better sometimes:
> `find /usr/src/linux/ -name "Kconfig" -exec grep {} -Hn -e "USB"`
>
> Someone told it wasn't correct to edit the .config directly (most
> probably because of depencies), but is it possible, at my own risk?Not sure, because I've never done it! I keep using make menuconfig for edits. To find a particular driver in the maze of the kernel tree you can of course spend hours studying it line by line, enabling and disabling each branch as you go along (in six months you'll know it all by heart). Alternatively, you could get a life and decide to press / while in menuconfig and enter some suitable search terms. Also, I often cat .config | grep -i <search_word> to find whether I have enabled something or other. After you compile a good kernel that does exactly what you want it to do, then copy its .config into any new kernel fs that you emerge and run make oldconfig instead. It'll prompt you for the changes and keep all your old settings which you know work. HTH. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
