When using genkernel 3.0-beta-somewhat, all my configs broke, even those already made with genkernel 1.8. this should be considered a bug. this happens only once, after that, the previous config is used. Workaraound for me was placing the file .config in / and adding --config-file=/.xxconfig to command line, xx the sources prefix. This cost me a whole night, as my kernels were extensively customized. GENKERNEL should *GENERALLY* repsect *ANY* previous .config, in *ALL* situations. Reproducible: Always Steps to Reproduce: 1. just emerge genkernel 2. execute genkernel 3. perfect kernel chaos. Actual Results: Had to boot from Livecd (as genkernel compiled not the custom but a standard configuration) to rectify the problem. Kernel was completely unusable. All .config in all /usr/src/* got lost (yes ALL). Expected Results: Never touch the configs unless changed by menuconfig. genkernel should backup all configs, unless they are changed by genkernel before, INSTEAD of killing them
my thoughts would be to put back the old style of saving the kernel in the /etc/kernels/ directory possibly still using the same directory structure as /usr/share/genkernel/ with the different arch's separated out but have each one be per the kernel name or even replace the "default" kernel config in /usr/share/genkernel with the one that is in /usr/src/(kernel version)/.config before the compile.
I think the emerge producing genkernel SHOULD by all means copy all .config from /usr/src to the genkernel configs. Everything else is too risky for inexperienced users upgrading to another Version of genkernel and busting all their config in the process. Also, when emerging new sources, this can be accounted by portage: Leave a copy in genkernels dir as default. I think genkernel NEVER should bring "default settings", but acquire those from the sources which are already there (possibly created by the user).
exactly though a default config for someone who does not have a config to pull in would be best let people have some place to start expecially the newbies...
Yeah, but I thought (have seen) that sources bring their own .config most of the time. Well just don't make genkernel DESTROY an already tried and true configs. If youre just going to chance APM or Graphics Settings to get what you want, it is POINTLESS to have genkernel replace everything with a default config. Some people do spend hours looking for "THE" config.
-no-config will prevent genkernel from overwriting your config files. we will be providing a way to backup files at some point.
I've been strugging to get a working kernel ever since this change! I've been doing a work arround by saving and loading my configs via menuconfig... I think this should be reopened with a slightly changed summary: have genkernel load and save kernel configs without overwriting or option to backup to unique file name
