Holly Bostick <motub <at> planet.nl> writes:
> I've actually been upgrading within a series (gentoo-sources, -r6 to > -r8), and across series (to ck-sources and mm-sources)... and been > paying attention closely to this exact issue when I did so. > And what I noticed is that when I switched the symlink and ran make > menuconfig, this was the message: > > mutable linux # make menuconfig (first time config of newly installed > mm-sources, booted into gentoo-2.6.11-r8) > HOSTLD scripts/lxdialog/lxdialog > scripts/kconfig/mconf arch/i386/Kconfig > # > *# using defaults found in /boot/config-2.6.11-gentoo-r8* > So in fact, makeoldconfig appears to be a bit obsolete, as the new > kernel used my old kernel settings as the default. This may be because I > had installed my kernel with make install, so there *was* a config to be > found in /boot, but it did save a lot of work. This make perfect sense. So using make install a syntax sequence would look like this? make menuconfig <select options and save> make && make modules_install cp arch/i386/boot/bzImage /boot/kernel-2.6.11-gentoo-r9 cp System.map /boot/System.map-2.6.11-gentoo-r9 cp .config /boot/config-2.6.11-gentoo-r9 Then the /boot/config* file is read between version numbers (linke 2.6.11-gentoo-r6 to 2.6.11-gentoo-r9)? But this does not work if I relinking to a new kernel series (such as 2.6.10 to a new 2.6.11 dir), that is I have to manually select the options each and ever one? Or is the /boot/config-2.6.10-gentoo-r4 file read by the new 2.6.11-gentoo-r6 series kernel? Last if I keep old kernels and configs around (ls /boot/): System.map-2.6.11-gentoo-r6 config-2.6.9-gentoo-r4d System.map-2.6.11-gentoo-r6B config-2.6.9-gentoo-r4e System.map-2.6.11-r6 grub System.map-2.6.9-gentoo-r4d kernel-2.6.11-gentoo-r6 System.map-2.6.9-gentoo-r4e kernel-2.6.11-gentoo-r6B boot kernel-2.6.11-r6 config-2.6.11-gentoo-r6 kernel-2.6.9-gentoo-r4d config-2.6.11-gentoo-r6B kernel-2.6.9-gentoo-r4e config-2.6.11-r6 it automagically knows the latest version of the config file to use? One twist. When I'm hacking at kernels (testing my own drivers and firmware and patches) I might stay with one one particular kernel for a while just to test the differences in patches, my hacks and my firmware) (This is acutally quite ugly, and I was looking for a gui tool to help me stay organized, so I can focus on C/assembler driver code....) So it'll know the difference between 'config-2.6.9-gentoo-r4d' and 'config-2.6.9-gentoo-r4e' ???? I doubt it.... This is why I need a tool or organizational methodology for kernel/driver/firmware hacking...... Please correct if I'm missing something? > For changing series, I definitely prefer to look at the kernel config > anyway, to see what options the series' patches have added, but for > upgrading within the same series, if nothing has really changed, it's > nice to know you can just make menuconfig, save immediately (because you > don't have to do anything, but you can also confirm that the settings > really are the same if you like), and head right into make > modules_install, etc. I find that actually faster than selecting X > number of new (and usually irrelevant to me) options with make oldconfig > anyway (n, n, n, etc). I agree with this but, I'd not bet that these changes only occur between different serias, (2.6.9 to 2.6.10) although that does seem to be the 'general guideline'....... All in all this is good information to know and confirms my suspicions..... Any Ideas are most welcome.... thanks HOLLY! James -- [email protected] mailing list
