On Fri, 2002-08-16 at 06:27, Richard G. Houser wrote: > I'm not certain this is such a bad thing, when installing another source > version, the sources go in the /usr/src/linux-x.y.zz directory, and a > simlink to the current kernel version is created into /usr/src/linux.
Are you *sure* about this? If so, doesn't it create RPM problems. OK, longwinded post alert... Let's imagine it's as you say. I start off with kernel-2.4.19.2mdk and kernel-source-2.4.19-2mdk. I do an urpmi --auto-select but don't upgrade the kernel. Now, by your reckoning, kernel-source-2.4.19-3mdk gets installed, and kernel-2.4.19.3mdk doesn't, as i've said. Now what happens is that the new source goes into /usr/src/linux-2.4.19-3mdk. Now what happens? Is /usr/src/linux-2.4.19-2mdk removed? If so, it's as I first thought - you end up with a source tree that doesn't match your kernel. If not, which is what you seem to be implying, OK - /usr/src/linux-2.4.19-2mdk sticks around, and /usr/src/linux remains a symlink to it. In terms of a working installation, this is much better. But since kernel-source-2.4.19-3mdk is a replacement of kernel-source-2.4.19-2mdk, kernel-source-2.4.19-2mdk doesn't exist any more. So what owns /usr/src/kernel-2.4.19-2mdk? Is it orphaned? Is it owned by kernel-source-2.4.19-3mdk now? What? Neither of those options seems particularly good. I tell you what - this machine is on kernel-2.4.19.2mdk and kernel-source-2.4.19-2mdk at the moment, i'll do an urpmi on the kernel-source package and see what happens. > Similar situation with the vmlinuz, intird, etc when installing a new > kernel (plus it gets added to the lilo config -- gotta remember to run > lilo after each -- otherwise bombs on my install of 8.2) Yeah, I realise this. -- adamw
