begin quote On Tue, 21 Oct 2003 10:44:36 -0700 "C. Brewer" wrote: > On Tuesday 21 October 2003 9:25, Thomas de Grenier de Latour wrote: > > > Because it is useful to be able to compile modules for a target > > kernel > > that may be different than the running kernel, and a symlink is a > > good way to point the target of your choice. > > Sure, that's an excellent point, but since the target kernel and the > running kernel are likely on the same machine, and the current state > of modules in portage IIRC isn't allowing the duplication of external > modules packages, why not just be booted into the one you're making > modules for? You're gonna end up rebooting either way eventually... Then fix pcmcia-cs and alsa-driver before you suggest anything. as it is, my machine won't boot properly without pcmcia-cs -and- alsa, as they IRQ conflict unless loaded in a certain order. They are both dependant on the target module, and theres no way in a gnomes purple hell you are going to get me into a state where I can reboot first, and then rebuild the modules, only to reboot again so I have a working boot session. uh-oh- NO. And no, you won't get me to emerge it with SLOT="purple-gnomes-2.4.44" either, Just because I sat down and got my own kerneltree installed into usr/src/testkernelwithextraJFSpatches , and then loose my existing , working, tried kernelset. When you get this set to -automagically- detect the target kernel., build modules and fix. then ok. if you want it to depend on the running kernel, erm... No. theres a few things already that do so, and that is -BROKEN- behaviour. I don't even -HAVE- the sources for my running kernel at most times. What? No I don't need them. I shouldn't need to have my sources for the hard compiled and working copy of 2.4.18-saviour with extra everything that I know boots all my machines and I have in a .tar stored away for working order. Yes, this thread invoked a lot of hot emotions from my side. // Spider -- begin .signature This is a .signature virus! Please copy me into your .signature! See Microsoft KB Article Q265230 for more information. end