Or just make install. That will update your boot loader for you and put stuff in /boot for you too! I did a make install before I did a make modules_install and ended up having to create /lib/modules/2.6.0 manually as a result. I also never got the qt based make xconfig working. The gconfig worked the first time. YMMV. That said, I haven't gotten the modules-init-tools yet, so I haven't actually booted my shiny new kernel yet. :-) Gerry -- Gerry Skerbitz gsker at tcfreenet.org http://www.kucinich.us On Thu, 18 Dec 2003, Benjamin Flaming wrote: > make menuconfig (for text-based configuration) > make xconfig (for GUI-based config using the Qt libraries - my preference) > or > make gconfig (for GUI-based config using the GTK+ libraries) > > Then: > > make (this builds the kernel and modules) > make modules_install (too obvious for comment) > cp arch/i386/boot/bzImage /boot/kernel-2.6.0 (install your new kernel) > > And finish by adding the appropriate lines to your boot-loader's > configuration, in order to add another boot option. This can be tricky at > first, but as long as you keep your old kernel available as a menu option, > you've got nothing to worry about. > > One thing to be aware of, is that you *will* need to install module-init-tools > if you use any modules in your 2.6 kernel. Source can be downloaded from: > > http://www.kernel.org/pub/linux/kernel/people/rusty/modules/ > > RPMs can be downloaded elsewhere. > > There are always a few other twists and turns, but I agree with the rest of > the comments - read the documentation and give it a try :) _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list