I've run into some strange behavior compiling a 2.6.2 kernel, hoping someone can shed some light.
I decided that for a new Gentoo install, I wanted to try out 2.6. I grabbed mm-sources and built it; things seemed ok except a *LOT* of error messages during boot (I thought 2.5 was supposed to be the development thread, and 2.6 is supposed to be "stable"?)... I also wanted to check out EVMS, and after a bit of searching, I've discovered that EVMS isn't really well integrated into the 2.6 kernel tree - I'd need patches. The patches failed to apply to my "mm" sources, so I emerged the plain 2.6.2 development sources. Problems continued, but I'll shelve my EVMS woes for the moment. On to my question.. I now have 2 source directories in /usr/src -- linux-2.6.2-mm1 and linux-2.6.2. All is good, I now want to configure/build the latter. I point /usr/src/linux at the linux-2.6.2, and then do make menuconfig. I was VERY disturbed to find that instead of a blank configuration, all of my previous selections (from the 2.6.2-mm1 kernel) had already been made! I exited and checked to make sure I was in the right source tree; I was. Yet I go back in and confirm that all of my choices are already there -- even the "neomagic" video driver, which I'll assume was not selected by the kernel developers. It gets worse. I build this new kernel, and after installing the kernel and modules (make install modules_install) the new kernel has been installed as vmlinuz-2.6.2-mm1 (overwriting my old one), when it was NOT from the 2.6.2-mm1 source tree! Also, it did NOT create a properly-named /lib/modules subdirectory, it used the old one, overwriting all the old modules! Why did this happen? How did the configuration of the old kernel source "infect" my new source tree? And more critically, how/WHY did the kernel from the new source tree pick up the same version *name* as the old one (with the "mm1")? Why would a person ever want this behavior? Is this a gentoo thing? --eeyore -- [EMAIL PROTECTED] mailing list
