On Feb 14, 2004, at 7:04 pm, Paul Vint wrote:
Christopher Robison wrote:
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?
My only guess would be that when you merged the new kernel source, portage copied your old .config file from /usr/src/linux. Just guessing though - I've never used emerge to install kernel source (I don't really see any advantage to it), I just go to kernel.org and get the vanilla source there. (That way makes patches easy too).
Maybe someone else can confirm if portage would copy a .config file? (I could understand if it did - I usually do that myself anyway ;)
I believe that's the case. Copying your old .config over to the new /usr/src/linux.whatever directory is generally desirable, IMO. But I can't address the OP's other complains - I'm guessing he's using Genkernel, and in that case I advise him to compile by hand instead. Portage can still handle emerging of the new sources if he does so.
Stroller.
-- [EMAIL PROTECTED] mailing list
