nate, Thanks for the reply. That's whats odd. (Remember I'm a total newbie here) I pulled the kernel building HOWTO off of the Debian site but most of the references were to RedHat so I'm a little confused. I tried to use make-kpkg but it kept failing so I did just like the HOWTO says:
make clean make xconfig make dep make make bzImage make modules - There weren't any make install - This is where it ran LILO for me??? What did I screw up?? The really weird thing is that it appears that the kernel image name that it built is just called Linux??? Thanks again! Barry deFreese NTS Technology Services Manager Nike Team Sports (949)-616-4005 [EMAIL PROTECTED] "Technology doesn't make you less stupid; it just makes you stupid faster." Jerry Gregoire - Former CIO at Dell -----Original Message----- From: nate [mailto:[EMAIL PROTECTED]] Sent: Friday, November 22, 2002 2:56 PM To: [EMAIL PROTECTED] Subject: RE: 2.4.18 SMP Kernel - Running but have a question deFreese, Barry said: > O.K. I compiled a new kernel with 2.4.18 SMP and I can now see both > processors under /proc/cpuinfo and I was able to build in the Compaq array > drivers. It is kicking butt. > > The question that I now have is that it appears to have re-configured and > re-run LILO for me but the kernel images is not in my /boot partition. > Should it have moved it or did I do something wrong?? the kernels ideally should reside in /boot, but theres no law that says it has to. if you built the kernel the 'debian way' with kernel-package and installed the resulting kernel-image-*.deb then it will take care of most of this. if you compiled from source without kernel-package then you should put the kernel in /boot and update lilo.conf(if needed, and re-run lilo) nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
