I just ran "make bzlilo" out of curiostiy... Pretty nifty command IF you use lilo. Heres the very end of it:
Code:
if [ -f /boot/vmlinuz ]; then mv /boot/vmlinuz /boot/vmlinuz.old; fi
if [ -f /boot/System.map ]; then mv /boot/System.map /boot/System.old; fi
cat arch/i386/boot/bzImage > /boot/vmlinuz
cp System.map /boot/
if [ -x /sbin/lilo ]; then /sbin/lilo; else /etc/lilo/install; fi
/etc/lilo.conf: No such file or directory
make[1]: *** [zlilo] Error 1
make: *** [bzlilo] Error 2
As you can see, it automatically copies your vmlinuz and system map for you then tries to run /sbin/lilo to update your bootloader. I'm thinking that had it found an /etc/lilo.conf on my system, it might have even made an entry for me as well.
In my opinon, it's a bad idea to teach like that.
If he isn't showing you the more "generic" way to compile a kernel then shame on him. I don't use lilo, thus that command isn't a good one for me to use. So his notes would probably have been:
make dep
make clean
make bzlilo
And well.... that's it probably. Next time, don't take so long on your break...
I did all this on a 2.6.13.2 kernel. I'm not seeing anywhere in the output where it made any modules. So, I would have to say you would also need to run "make modules" and "make modules_install" too. So it might have been something like:
make dep
make clean
make bzlilo
make modules
make modules_install
Find a cute girl or guy in your class and ask them for what you missed... Also, be aware that "make dep" is an obsolete command with regards to a 2.6.xx kernel.