Phil H wrote: > So you just need one (any) kernel compiled with CONFIG_MODULES=y and > CONFIG_BLK_DEV_LOOP=n, and running that you can compile loop.o drivers for > some other kernel 2.x.y for which you have the sources configured, however > this kernel 2.x.y for which you are building the loop.o does NOT need to > be configured with CONFIG_MODULES=y and CONFIG_BLK_DEV_LOOP=n? > > That is correct? Any kernel that "works", i.e. supports your computer hardware and file systems, can be used to compile any other kernel regardless of their configurations. (Some really ancient kernel sources may require equally ancient gcc + binutils versions, but that is not relevant here) One pitfall is that if you compile and install differently configured kernel that has exactly same kernel version and EXTRAVERSION (i.e. same `uname -r`) as your running kernel, and insmod those newly compiled modules to your running kernel, then you end up with modules running in kernel space but compiled using WRONG configuration. Changing EXTRAVERSION in kernel Makefile before compiling kernel is easy way to avoid this pitfall. That way newly compiled and installed modules will not overwrite modules of your running kernel. Compiling kernel+modules using same `uname -r` as your running kernel, but NOT installing them, is not a problem. -- Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
