Again and again I see people spew all kinds of weird stuff about genkernel, according to some of them it eat little babies apparently and enjoys it. What seems to be the primary reason for the confusion is that running genkernel all will pull in a default LiveCDish .config file and compile the kernel with that. This among other things, make people think that genkernel can detect and generate .config files based on your running system and since it's a LiveCDish kernel they think the program is broken. It also creates the issue that people don't think they can use custom kernel configurations with genkernel. While I do call these people stupid (primarily because you can't even explain tot hem they are wrong), I also have to admit that genkernel ignores the human element in how it works and it would be possible to change the behavior in minor ways to clean up the most common misconceptions. Genkernel Myth 1: It *generates* .config files When genkernel pulls in a bundled .config some more information, maybe even a yes/no prompt is needed. Genkernel myth 2: You can't use custom kernels When /usr/src/linux/.config exist and gets ignored it confuses people, thinking it's not possible to have custom configurations or that "genkernel wiped my configuration!!!", we all know it makes a backup. Do we have a /etc/kernels/* configuration we would use here? Have to be careful here, I don't want to break how things work for us thats used it for ages, but if we have /usr/src/linux/.config, no /etc/kernels/* maybe the default shouldn't be to pull in the bundled kernel. Or at least ask first. Genkernel Myth 3: Only stupid people uses genkernel. I think this myth is created because people thinks genkernel generates tailor made .config files, instead of you having to be "smart" and do a custom kernel. Myth 1 and 2's solution seems like it would clear this one up too. Reproducible: Always
I'm really not sure what you want us to do here. You can't fix stupid (at least according to Ron White).
