Summary: | sys-kernel/genkernel-3.2.0_pre11 changes .config file | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | Alon Bar-Lev (RETIRED) <alonbl> |
Component: | genkernel | Assignee: | Gentoo Genkernel Maintainers <genkernel> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Alon Bar-Lev (RETIRED)
2005-06-25 10:06:13 UTC
We're not going to implement --do-not-touch-config since some things *have* to be on for anything to remotely work. The ext2/3 issue you bring up is valid however, and we do need to disable that check if you are generating an initramfs image. I am glad!!! I suggested the --do-not-touch-config since it was the simplest way to go (not the best...) 1. As I understand genkernel always depends on initrd... right? If I specify the bzImage or kernel it just to reduce time for compilation. 2. Please consider to analyze the .config file and warn or error when invalid options were detected... So that the user may change this him-self. Thanks Again! I've seen what you done in pre14. It is fine for me! But I still think that modifying the .config cause advanced users to lose control... So my last request is to consider --strick that warns the user if genkernel is not happy with configuration... without modifying it. If you wish to add that behavior that is fine please send us a patch. However we would get more bug reports stating genkernel is broken if we do not enable the few options that we do. The only options currently are for dmraid/lvm modules to be compiled for that filesystem support. |