Kernel Compilation, and "vmlinuz-2.2.2" and guide

[khokhar]

The operating system is Redhat 7.0. I am using a guide
"http://howto.lansystems.com/index.php?howto=kernel_compile_and_upgrade_guide"
to complie kernel. But i face a problem. The steps i performed are

1- move the new linux kernel source at directory /usr/src with name /linux-2.2.2
2- Create a symbolic link to this directory /usr/src/linux-2.2.2.
3- make menuconfig (and adjusted settings)
4- make dep
5- make clean
6- make bzImage
7- make modules
8- make modules-install

Every thing is fine and according to the guide. but the next step in guide is
cp /usr/src/linux-2.2.2/arch/i386/boot/bzImage/vmlinuz-2.2.2
The problem I faced is that
I have not such a file "vmlinuz-2.2.2" and also /bzImage is not a directory rather a file,
so would u tell me from where i am wrong or my guide.
Also i don,t know where to copy this file.
my current working directory is /usr/src/linux-2.2.2
Have a nice Wishes for my new GUIDER.

[twofoolish2b]

What you want to do is copy bzImage to /boot or wherever you want to put it. When I compile a kernel this is what I do:

1. cp linux-2.x.x.tar.gz /usr/src
2. rm linux
3. tar xvzf linux-2.x.x.tar.gz
4. mv linux linux-2.x.x
5. ln -s linux-2.x.x linux
6. cd linux
7. make xconfig
8. make dep
9. make clean
10. make bzImage
11. make modules
12. mv /lib/modules/2.x.x /lib/modules/2.x.x.old
13. make modules_install
14. mv /boot/System.map /boot/System.map.old
15. mv /boot/bzImage /boot/bzImage.old
16. cp /usr/src/linux/System.map /boot
17. cp /usr/src/linux/arch/i386/bzImage /boot
18. edit lilo.conf
19. run lilo form the command line
20. reboot

[demian]

As an addition: The compressed image of the kernel after the compilation is named bzImage or zImage depending on whether you used make bzImage or make zImage. Traditionally the kernel image you boot (which you move to /boot) is renamed vmlinuz (possibly with an additional version number appended).
So you might need to replace step 15 is the above list with
mv /boot/vmlinuz /boot/vmlinuz.old

You can, of course, name your kernel image whatever you like. Just make sure that the name you have in your /etc/lilo.conf matches the actual kernel image name.