"Code Listing 4.2: Copying over the Installation CD kernel config" is causing issues for people, in that genkernel is failing to build due to some config variable cruft that may (or may not) be in the livecd or livedvd kernel configs. Please see the original issue reported in bug 378667 .. in addition to this bug i saw two others report this issue in the last 24h in #gentoo Genkernel includes kernel-config files already for every arch, and since genkernel is used to build the livecd kernels (afaik) there is no particular advantage to using the one directly on the livecd as they are most likely very similar if not the same. In addition, there is nothing that would keep this copied-from-livecd file around after genkernel gets upgraded, and so if a user is expected to always use the livecd's kernel config then they would have to be expected to copy it every time genkernel upgrades (since these files are not CONFIG_PROTECT'ed). Further, there is nothing to say that a user isn't trying to use a really old (2008.0) livecd with a new (say, 3.0) kernel and >=3.4 genkernel, and while following the handbook, would run into issues even more extreme than the one seen in the aforementioned bug. From a testing perspective, I believe it would also be much easier to do QA on the genkernel-installed kernel-config files as new kernels are rolled out, as dev's can test the genkernel package directly with these sources and revbump as necessary with new configs when they require changing; there is no such means of QA with the livecd kernel configs. As such, I owuld like to request that Code Listing 4.2 in Section 7.d of the handbook (and its related text) should be removed. Reproducible: Always
genkernel folks, would it be possible to confirm this? Is it okay if the docs are altered to just use ~# emerge genkernel ~# genkernel all instead of ~# emerge genkernel ~# zcat /proc/config.gz > /usr/share/genkernel/arch/x86_64/kernel-config ~# genkernel all If so, I'll update the docs to reflect this.
The config shipped with genkernel should work. If it doens't, that's a different bug. I vote for updating docs to ~# emerge genkernel ~# genkernel all I hope assigning back to you is alright.
Yup. Fixed in CVS, should show up on the site in an hour or so. Thanks for reporting!
