make is the same as make bzImage and make modules. The diffrenece between 2.4 and 2.6 is taht you don't need to make dep.

If I may ask one more question regarding compiling the new kernel.....As I mentioned, when I tried to boot the new kernel, it would not boot but when straight to a black screen and froze, no processor or hard drive activity.

The question I want to ask is this: When in menuconfig, during the processor selection I chose the AMD64/Opteron (which is what I have AMD64 3400+). During compilation and make everything seemed OK, but I am wondering choosing support for the AMD64 meant that the kernel was looking for 64 bit software and didn't find it or some other conflict in the regard.

If this is a silly question, please pardon it, but I am not sure how to resolve an unbootable kernel.

Any thoughts greatly appreciated.

Bob

Did you compile framebuffer support into the kernel? Black screen is usual problem with not compiling it.
I don't have a 64 bit processor, but I believe that this couldn't cause the problem because 64 bit processors should be compatible with 32 bit software.

Thank you for replying. I do not recall seeing an option to compile framebuffer support in menuconfig. Is it possible to configure the kernel again or do I have to remove it, dowmload it again and start over? If I have to remove it, what is the command line syntax?

Thanks again,

Bob

Open your kernel directory in /usr/src/kernel-version, backup your config file, then run make clean and make menuconfig again. You don't have to remove kernel source, make clean cleans compiled things from your source directory. Then run make bzImage and copy your new kernel into boot directory. Add new entry in lilo.conf for this kernel and run lilo. That's all.

I will try that now...Thanks again for your help. Hope it works this time.

Bob

rkrishna:
Symlinks have nothing to do with security. What matters is the permisions on the actual device. Symlinks only serve as mnemonics so that users don't have to know that /dev/hdc is the cdrom drive. Most of the time, it is referenced by the mount point anyway.

Usage of the CD is dependent on physical access. There is no security measure that can defend against an attack based off of physical access.

Please stop using unreadable AOLspeak as well.

I beleive you are correct in your assumtions that the newer kernels may not require those files/symlinks, but some software still does...Or at least, it makes it alot easier for me to type when compiling wlan-ng, for instance, '/usr/src/linux' rather than '/usr/src/downloaded/kernels/linux-2.6.15'......

Sometimes, keeping the old conventions can help stave off a BAD headache...lol

So, also, is the 'make && make modules_install' as compared to 'make bzImage && make modules && make modules_install' argument. I prefer to just type 'make && make modules_install' then copy the .config, System.map and bzImage to /boot.

Just my two cents

Good point there cwwwilson, I've tried software that looks in /usr/src/linux that would balk if it wasn't there (unlike wlan-ng which is good enough to let you specify a location).

The only reason I use "make bzImage && make modules" as opposed to just "make" is that "make" builds a bunch of other things too (outlined in "make help"). As I said before, seems everybody has their own particular way of doing it. Eh, to-may-to / to-mah-to I guess .

I followed, these instructions, I believe to the letter. Somehow, I have altered the boot records and the system no longer boots to either kernel. If (a big if) I am able to restore it somehow without a complete reinstall, I concede that I am not quite ready to tackle building a new kernel. I will need a lot more understanding of whole process, and, if something like this happens again, I will at least be able to boot into the original.

Thanks for your help.

Bob

I suggested make bzImage only because command make modules was not necessary. They already were built and installed.