On Tuesday 12 July 2005 01:36, James D. Parra wrote:
Hello,
How is this possible?
Okay, I copied /usr/src/linux-2.6.11.4-21.7 to /usr/src/linux-2.6.11.4-21.7.custom, ran "make menuconfig" (made my changes here so could use the new ATTO SCSI card) from the *custom directory, saved it, ran "make", then " make modules_install", created all the images and soft links under boot (below), edited lilo.conf and ran "lilo", rebooted, lilo says it is going to boot the new kernel, but instead of seeing my new kernel being loaded it says the default kernel is loaded; uname -r 2.6.11.4-21.7-default. However, that can't be possible because I now have access to my the tape drive attached to the ATTO SCSI card which I never had access to before when booting the other kernels. I have included relevant info below. Any ideas on what happened? I was hoping the kernel would be, 2.6.11.4-21.7-bigsmp.custom.
Well, think about this a little. The kernel you got in the installation wasn't "default" it was "bigsmp". I don't know where you got the modules directory bigsmp.custom from, but it doesn't look like it was generated by the compile, judging by the dates on the directories The name of the kernel (the uname name, not the file name) is not taken from the name of the source directory, it's created by the Makefile in your source directory. The short story is: if you want to have a text tagged on to the kernel name, such as "atto" or "custom", you can create a file in the source directory called "localversion", containing the text you want to use The "default" name you got is just that, the default name. It doesn't mean you're using the same kernel as before, because you never had the -default kernel installed