On Mon, Feb 12, 2001 at 03:46:34PM -0800, Spencer Underground wrote: > if I change > some parameters in my XF86config file, did I just recompile the kernel? No. The configuration options you set using `make config` (or meunconfig or xconfig) are used to control the compilation process. If you set option X to on, the relevant code is compiled into the kernel; if it is off, the code is not put into the kernel. Once vmlinuz has been built, the config files are never referenced again unless you use them as a set of baseline settings for a future kernel build. > If I reconfigure LILO, did I recompile. No. The lilo config just tells the system where to find the kernel during the startup process. > Does complilation only refer to the vmlinuz file? "Compilation" refers to the process of _creating_ vmlinuz. From a non-programmer's viewpoint, "compiling" generally means "using the make command". In the course of building a kernel, I generally use make 5 times: make menuconfig - compiles the menu-based configuration program and runs it make clean - deletes old files make bzImage - compiles the kernel make modules - compiles any modules I've configured make modules_install - copies new modules to correct locations A more accurate way to know when you're compiling is to watch for messages that look like gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -DLOCALE -DCURSES_LOC="<ncurses.h>" -c -o lxdialog.o lxdialog.c gcc is the GNU C compiler. If gcc is invoked, you're compiling. If it isn't, you're not. (More or less. gcc can do a couple other things and there are other compilers out there. But, for most users under Linux, this rule holds true well over 90% of the time.) -- SGI products are used to create the 'Bugs' that entertain us in theatres and at home. - SGI job posting Geek Code 3.1: GCS d? s+: a- C++ UL++$ P++>+++ L+++>++++ E- W--(++) N+ o+ !K w---$ O M- V? PS+ PE Y+ PGP t 5++ X+ R++ tv b+ DI++++ D G e* h+ r y+