On 4/20/05, Temlakos <temlakos@xxxxxxxxx> wrote: > Rick Stevens wrote: > > Antonio Olivares wrote: > > > >> Dear all, > >> I was afraid to update to a newer kernel with all > >> the messages that the system won't boot but I am > >> taking a risk. I have downloaded 2.6.11.7.tar.bz2 and > >> extracted it. I read the README and have done the > >> following: > >> make mrproper > >> make xconfig > >> make dep > >> make clean > >> make bzImage > >> > >> What else do i need to do? I am still running > >> 2.6.9-1.667. I need to manually edit /boot/grub.conf > >> to put the new kernel. > >> What advice can you give me? > >> > >> Do I need to do a modules install? or something like > >> that. > >> > >> I appreciate all the help that you can provide. > > > > > > You don't need the "make dep" or "make clean" steps with 2.6 kernels. > > Simply: > > > > make mproper > > make xconfig > > make bzImage > > make modules > > make modules_install > > make install > > > > That should do it all for you. Double check your /boot/grub/grub.conf > > file to verify that the new kernel got installed. > > > > Of course, why don't you just "yum update kernel" and use the > > precompiled binary 2.6.11 kernel for FC3 from the official repositories? > > I can't speak for Antonio; maybe he has plunged into Fedora and hasn't > mastered the rpm and yum commands. (/I/ still have trouble with them, > sometimes.) But I have heard that compiling from source gives you an > application, or a kernel, optimized for your machine in a way no binary > can match. Is that true? If it is, then those instructions will prove > very valuable. > > Then, too, there's the matter of wanting to load into the kernel certain > non-standard modules, and even to run the kernel in four-stack mode for > some purposes. (NDISwrapper springs to mind.) I'd like a quick how-to on > that alone, or at least a link to some clear instructions. > > Temlakos > After you unpack the tarball read the README file. It will provide you with the necessary instructions on building the kernel. That is the easy part. The hard part is customizing the kernel whether to enable/disable modules or to improve performance. To do that you need to know your hardware and the type of software you are using or planning to use. In comparison to the 2.4 series the 2.6 developers have really done an excellent job in reworking the config tools. The xconfig/gconfig GUI makes setting the configuration options an easy case of point and click.
