3/16    debian newbie question. so i compiled a new kernel (2.4.18,
        2.4.19, 2.6.0) but when i boot with it, the modules no longer
        work, if i link /lib/modules/.... to the correct kernel name,
        it complains that the modules are not compiled for 2.4.18-bf2.
        So what is the correct way to try a new kernel on linux for
        debian? thx.
        \_ In general, compiling source requires "make bzImage;make modules;
           make modules_install;make bzlilo(or whatever you do to let your
           boot loader load the kernel). make modules_install will install
           the modules ot /lib/modules.  The debian way is make_kpkg
           kernel_images to create the deb package and install using dpkg.
           \_ you mean make-kpkg clean; make-kpkg kernel_image;
              cd ..; dpkg -i <kernel_package>
              \_ exactly.  which boot manager are you using?
           \_ another newbie question, i ran make modules, all works. then
              I ran make modules_install, I got

find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
if [ -r System.map ]; then /sbin/depmod -ae -F System.map  2.4.19; fi
depmod: *** Unresolved symbols in /lib/modules/2.4.19/kernel/drivers/net/wan/wanpipe.o
depmod:         register_wan_device_Rsmp_25269802
depmod:         lock_adapter_irq_Rsmp_7e6ae263
depmod:         wanrouter_encapsulate_Rsmp_a5336dd5
depmod:         unlock_adapter_irq_Rsmp_1e7b9a43
depmod:         unregister_wan_device_Rsmp_0ebe03d1
depmod:         wanrouter_type_trans_Rsmp_5cb5fb99
make: *** [_modinst_post] Error 1

             Is this something to be ignored or??

        \_ btw, you may want to use some newer kernels that don't have the
           variety of local exploits reported in recent weeks.
           \_ such as? what version do you recommend?
              \_ like, say, the latest? or at least get a version with the
                 backported patches.
                 \_ get the source for 2.4.25-1 if you want to use 2.4
                    \_ exchange known security holes for unknown bugs/holes.
                       \_ or exchange new unknown bugs/holes for old
                          unknown bugs/holes.
           \_ use the 2.4.18-1-foo debian kernel. (where foo is your
              processor) When linux kernel exploits are found, the debian
              security team back-ports the patches and release an updated
              2.4.18 kernel-image. This way you don't have to deal with any
              of the hassles involved with compiling a kernel. nor do you
              have to wait for testing/unstable to releases the next kernel
              version. and by using the same kernel version, you're not
              forced to upgrade libraries and api's required by the new
              kernel.
              \_ it's not really a big hassle, once you've learned how.
                 and debian's kernel is not going to be nearly as optimized
                 as one you build yourself. ergo, the whole point of wanting
                 to build your own kernel.